| From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: notification: pg_notify ? |
| Date: | 2002-03-22 07:06:36 |
| Message-ID: | 1016780796.7733.78.camel@jiro |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2002-03-21 at 23:41, Christopher Kings-Lynne wrote:
> > > Exactly what semantics do you have in mind?
> >
> > The current syntax I'm using is:
> >
> > NOTIFY condition_name [ [WITH MESSAGE] 'my message' ];
> >
> > But I'm open to suggestions for improvement.
>
> Have you considered visiting the oracle site and finding their documentation
> for their NOTIFY statement and making sure you're using compatible syntax?
Oracle's implementation uses a completely different syntax to begin
with: it's called DBMS_ALERT.
> They might have extra stuff as well.
From a brief scan of their docs, it doesn't look like it. In fact, their
implementation seems to be worse than PostgreSQL's in at least one
respect: "A waiting application is blocked in the database and cannot do
any other work."
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-03-22 07:10:38 | Re: notification: pg_notify ? |
| Previous Message | Ross J. Reedstrom | 2002-03-22 06:54:10 | Re: SET NULL / SET NOT NULL |