Re: notification information functions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: notification information functions
Date
Msg-id 6652.1211141130@sss.pgh.pa.us
Whole thread Raw
In response to notification information functions  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: notification information functions  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> I suggest:

> pg_listened_events(out event name) returns setof record
> pg_pending_events(out  event name, out message text) returns setof record

> The first would show events being listened on by the current backend, 
> while the second would show all pending events for the current db.

pg_listened_events seems reasonable, but what's a "pending event"?
If you mean stuff that hasn't yet been removed from the shared circular
buffer, it seems like that would be too transient (not to mention
implementation-dependent) to be interesting.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: notification information functions
Next
From: Andrew Dunstan
Date:
Subject: Re: notification information functions