Protocol forced to V2 in low-memory conditions?

From: Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Protocol forced to V2 in low-memory conditions?
Date: 2013-09-09 23:08:30
Message-ID: CAOtHd0C=sRitHx2GSPgoK2t1A70QJk4HB59QvB_pmMR7zaecgw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-09-09 23:39:00 Re: memory usage of pg_upgrade
Previous Message Tom Lane 2013-09-09 22:53:36 Re: lcr v5 - introduction of InvalidCommandId