On Mon, Jun 13, 2016 at 10:27 PM, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > Modulo that last point, here is a patch that shows how I think this could > work, in combination with the patch I posted previously that sets the > "client encoding" in the parallel worker to the server encoding. > > This patch disassembles the NotificationResponse message with a temporary > client encoding, and then sends it off to the real frontend using the real > client encoding. > > Doing it this way also takes care of a few special cases that > NotifyMyFrontEnd() handles, such as a client with protocol version 2 that > doesn't expect a payload in the message.
How does this address the concern raised in the last sentence of https://www.postgresql.org/message-id/CA+TgmoaAAEXmjVMB4nM=znf_5b9jhuim6q3afro4spt23ti...@mail.gmail.com ? It seems that if an error occurs between the two SetClientEncoding calls, the change will persist for the rest of the session, resulting in chaos. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
