From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: notification information functions |
Date: | 2008-05-18 20:09:40 |
Message-ID: | 48308D04.3080800@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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.
>
>
>
Fair enough. I'm all for less work ;-)
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-05-18 20:32:37 | ERRORDATA_STACK_SIZE panic crashes on Windows |
Previous Message | Tom Lane | 2008-05-18 20:05:30 | Re: notification information functions |