Re: notification information functions - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: notification information functions
Date
Msg-id 48308D04.3080800@dunslane.net
Whole thread Raw
In response to Re: notification information functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:
> 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.
>
>             
>   

Fair enough. I'm all for less work ;-)

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: notification information functions
Next
From: Tom Lane
Date:
Subject: ERRORDATA_STACK_SIZE panic crashes on Windows