head	1.4;
access;
symbols;
locks; strict;
comment	@# @;


1.4
date	92.07.14.05.54.17;	author ptong;	state Exp;
branches;
next	1.3;

1.3
date	92.06.17.22.04.15;	author mer;	state Exp;
branches;
next	1.2;

1.2
date	92.03.25.19.34.02;	author clarsen;	state Exp;
branches;
next	1.1;

1.1
date	92.03.25.19.26.11;	author clarsen;	state Exp;
branches;
next	;


desc
@async docs.
@


1.4
log
@reformated
@
text
@.\" XXX standard disclaimer belongs here....
.\" $Header: /home/postgres/mer/refs/postquel/RCS/notify,v 1.3 1992/06/17 22:04:15 mer Exp ptong $
.SP "NOTIFY" COMMANDS 3/25/92
.XA 2 "Notify"
.uh NAME
.lp
notify \(em Signal all frontends and backends listening on a relation
.uh SYNOPSIS
.lp
.(l
\fBnotify\fR relation_name
.)l
.uh DESCRIPTION
.lp
.b notify
is used to awaken all backends and consequently all frontends
listening on the relation
.b relation_name.

This can be used either within a tuple level rule as part of the
action body or from a normal query.  When used from within a normal
query, this can be thought of as IPC.  When used from within a rule,
this can be thought of as the alerter mechanism.

.uh "SEE ALSO"
.lp
definerule(commands), listen(commands), libpq.
.uh BUGS
@


1.3
log
@fix a macro call
@
text
@d2 1
a2 1
.\" $Header: /home1/frew/s2k/postgres/ref/=postquel/RCS/notify,v 1.2 1992/03/25 19:34:02 clarsen Exp $
d10 3
a12 2
.b "notify"
relation_name
d27 1
a27 3
definerule(postquel).
listen(postquel).
libpq.
@


1.2
log
@cosmetics
@
text
@d2 1
a2 1
.\" $Header: RCS/notify,v 1.1 92/03/25 19:26:11 clarsen Exp Locker: clarsen $
d7 1
a7 1
notify \*(- Signal all frontends and backends listening on a relation
@


1.1
log
@Initial revision
@
text
@d2 1
a2 1
.\" $Header$
d14 1
a14 2
.b listen

d22 1
a22 1
this can be thought of as alerters.
@