Re: implementing an out-of-transaction trigger

From: Greg Stark <gsstark(at)mit(dot)edu>
To: "Iain" <iain(at)mst(dot)co(dot)jp>
Cc: "Mike Rylander" <mrylander(at)gmail(dot)com>, <pgsql-sql(at)postgresql(dot)org>
Subject: Re: implementing an out-of-transaction trigger
Date: 2004-09-16 03:57:39
Message-ID: 87sm9irhl8.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


"Iain" <iain(at)mst(dot)co(dot)jp> writes:

> Though, as far as I can tell, there is no way to have the notify activate a
> pl/pgsql function directly. I'll still need to write a client program to
> create a session and actually do the listening, that is if I havn't missed
> anything else...

Right, presumably some sort of daemon that sits and waits for events. Much
like you would have with Oracle advanced queuing and such.

The big difference is that NOTIFY doesn't pass along any parameters. You will
need some way for your daemon to find any pending data it needs to process.
You might need some kind of queue table, or you might be able to get by
without one.

--
greg

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Iain 2004-09-16 05:15:39 Re: implementing an out-of-transaction trigger
Previous Message Iain 2004-09-16 02:02:25 Re: implementing an out-of-transaction trigger