On Wed, Oct 14, 2015 at 7:34 AM, Robbie Harwood <rharw...@redhat.com> wrote: > Alright, here's v3. As requested, it's one patch now. Other things > addressed herein include: > Essentially, the problem is that socket_putmessage_noblock() needs to > know the size of the message to put in the buffer but we can't know > that until we've encrypted the message. socket_putmessage_noblock() > calls socket_putmessage() after ensuring the call will not block; > however, other code paths simply call directly into socket_putmessage() > and so socket_putmessage() needs to have a path to encryption as well. > > If you have other potential solutions to this problem, I would love to > hear them; right now though I don't see a better way. > > Patch follows. Thanks!
After giving a quick shot at this patch, I am still seeing the same problem: psql: lost synchronization with server: got message type "S", length 22 (And unpatched works, I will try to put my head into your code...) Regards, -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
