Re: Listen / Notify - what to do when the queue is full
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jeff Davis <pgsql@j-davis.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-09T22:30:29Z
Lists: pgsql-hackers
On Tue, Feb 9, 2010 at 4:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Jeff Davis <pgsql@j-davis.com> writes: >> Looking at the documentation, it appears that all of the server >> encodings represent 7-bit ascii characters using the same 7-bit ascii >> representation. Is that true? > > Correct. We only support ASCII-superset encodings, both for frontend > and backend. > > Limiting NOTIFY payloads to 7-bit would definitely avoid the issue. > The question is if that's more of a pain than a benefit. I think it's a reasonable restriction for now. We have limited time remaining here; and we can always consider relaxing the restriction in the future when we have more time to think through the issues. It'll still be a big improvement over what we have now. ...Robert