| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Andrew Chernow <ac(at)esilo(dot)com>, Joachim Wieland <joe(at)mcknight(dot)de>, Greg Smith <greg(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Arnaud Betremieux <arnaud(dot)betremieux(at)keyconsulting(dot)fr> |
| Subject: | Re: Listen / Notify - what to do when the queue is full |
| Date: | 2010-02-10 01:32:14 |
| Message-ID: | 4B720C9E.8050400@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:
>
>> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-02-10 01:38:29 | Re: Listen / Notify - what to do when the queue is full |
| Previous Message | Tom Lane | 2010-02-10 01:22:50 | Re: Listen / Notify - what to do when the queue is full |