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

From Tom Lane
Subject Re: Protocol forced to V2 in low-memory conditions?
Date
Msg-id 17763.1378821195@sss.pgh.pa.us
Whole thread Raw
In response to Re: Protocol forced to V2 in low-memory conditions?  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Protocol forced to V2 in low-memory conditions?
Re: Protocol forced to V2 in low-memory conditions?
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2013-09-10 12:31:22 +0200, Magnus Hagander wrote:
>> On Tue, Sep 10, 2013 at 5:29 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> I've been thinking of late that it might be time to retire libpq's
>>> support for V2 protocol (other than in the specific context of the first
>>> error message received while trying to make a connection).

>> It's probably worth polling for that. I believe the jdbc driver at
>> least has code for it, but I don't know if it's a requirement at this
>> point.

> Yes, it has code for it and I think it's still used pretty frequently to
> circumvent prepared statement planning problems (misestimation,
> indeterminate types). So I think we need convincing reasons to break
> their usage.

Note that I was proposing removing libpq's support for V2 connections.
Not the backend's.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: New statistics for WAL buffer dirty writes
Next
From: Magnus Hagander
Date:
Subject: Re: Protocol forced to V2 in low-memory conditions?