Re: Listen / Notify - what to do when the queue is full

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Jeff Davis <pgsql@j-davis.com>, Andrew Chernow <ac@esilo.com>, Joachim Wieland <joe@mcknight.de>, Greg Smith <greg@2ndquadrant.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, "Florian G. Pflug" <fgp@phlo.org>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org, Arnaud Betremieux <arnaud.betremieux@keyconsulting.fr>

Date: 2010-02-10T01:32:14Z

Lists: pgsql-hackers


Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>   
>> Jeff Davis wrote:
>>     
>>> So, I think ASCII is the natural choice here.
>>>       
>
>   
>> It's not worth hanging up this facility over this issue, ISTM. If we 
>> want something more that ASCII then a base64 or hex encoded string could 
>> possibly meet the need in the first instance.
>>     
>
> Yeah, that would serve people who want to push either binary or
> non-ASCII data through the pipe.  It would leave all risks of encoding
> problems on the user's head, though.
>
> 			
>   

True. It's a workaround, but I think it's acceptable at this stage. We 
need to get some experience with this facility before we can refine it.

cheers

andrew