Re: Listen / Notify - what to do when the queue is full - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Listen / Notify - what to do when the queue is full
Date
Msg-id 1124f3c0304cda4eeca292afc3518755@biglumber.com
Whole thread Raw
In response to Re: Listen / Notify - what to do when the queue is full  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: Listen / Notify - what to do when the queue is full  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


>>> - do we need to limit the payload to pure ASCII ? I think yes, we need
>>> to. I also think we need to reject other payloads with elog(ERROR...).

>...[snip other followups]

On the one hand, I don't see the problem with ASCII here - the
payload is meant as a quick shorthand convenience, not a literal payload
of important information. On the other, it should at least match
the current rules for the listen and notify names themselves, which
means allowing more than ASCII.

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 201001102303
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAktKo40ACgkQvJuQZxSWSshg9ACg2uiDYuhBnRQqFS6Ej3O9VLcC
2TgAn035OrYcdERn4I1VI4NRQFBIcXZ/
=yJmK
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: quoting psql varible as identifier
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: Testing with concurrent sessions