Postgres Pro
Downloads
Home   >   mailing lists

Protocol forced to V2 in low-memory conditions? - Mailing list pgsql-hackers

From Maciek Sakrejda
Subject Protocol forced to V2 in low-memory conditions?
Date
Msg-id CAOtHd0C=sRitHx2GSPgoK2t1A70QJk4HB59QvB_pmMR7zaecgw@mail.gmail.com
Whole thread Raw
Responses Re: Protocol forced to V2 in low-memory conditions?
List pgsql-hackers
Tree view
One of our customers seems to be running into exactly the issue hypothesized about by Tom here:

http://www.postgresql.org/message-id/8040.1314403175@sss.pgh.pa.us

That is, the server is in low-memory conditions, and the client occasionally issues an error saying it can't complete a certain action due to the protocol version:

PG::UnableToSend: function requires at least protocol version 3.0: SELECT ...

The server is 9.2.4, and the client is the Ruby pg gem using a 9.2.4 libpq.

Was the possibility of an inadvertent protocol downgrade addressed as part of that patch? I read through the thread, but it wasn't entirely clear.

Thanks,
Maciek

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: lcr v5 - introduction of InvalidCommandId
Next
From: Bruce Momjian
Date:
Subject: Re: memory usage of pg_upgrade