| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Judith Retief <JudithR(at)inet(dot)co(dot)za> |
| Cc: | "'Brett Schwarz'" <brett_schwarz(at)yahoo(dot)com>, "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: sql listen fails using libpgtcl |
| Date: | 2006-02-01 14:26:39 |
| Message-ID: | 29654.1138803999@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Judith Retief <JudithR(at)inet(dot)co(dot)za> writes:
> But I think I've identified my problem in any case. I've been trying to
> limit the downtime of the functionality that this script provides by running
> it from its new location while the live one is still running - connected to
> the same db. So since the live one has already registered a callback on
> these events, the test script don't get any notifications, I assume?
No, NOTIFY delivers an event to *each* active listener for the given
event name.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Judith Retief | 2006-02-02 04:17:59 | Re: sql listen fails using libpgtcl |
| Previous Message | Judith Retief | 2006-02-01 05:37:36 | Re: sql listen fails using libpgtcl |