| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: LISTEN & transactions |
| Date: | 2001-12-02 16:29:27 |
| Message-ID: | 23007.1007310567@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
"Jeroen T. Vermeulen" <jtv(at)xs4all(dot)nl> writes:
> I can use the existing behaviour in libpqxx[1] to guarantee that a
> trigger handler is always able to start a transaction on the connection
> the notification came in on. But that probably wouldn't make much sense
> (though it would still be possible) unless the current way of doing
> things is here to stay.
Should be okay to depend on the fact that notifies are only delivered
between transactions; see the NOTIFY reference page.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dsmclennan | 2001-12-03 04:57:22 | C interface libpq.so.2 problem |
| Previous Message | Jeroen T. Vermeulen | 2001-12-02 15:57:39 | LISTEN & Transactions (oops!) |