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 513.1378996512@sss.pgh.pa.us
Whole thread Raw
In response to Re: Protocol forced to V2 in low-memory conditions?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Protocol forced to V2 in low-memory conditions?
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 09/11/2013 02:30 PM, Robert Haas wrote:
>> On Tue, Sep 10, 2013 at 9:53 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Note that I was proposing removing libpq's support for V2 connections.
>>> Not the backend's.

>> I vote against this.  If we remove V2 support from libpq, then we'll
>> have no easy way to test that the backend's support still works.

> How is it tested now, and who is doing the testing?

Exactly.  The current support in libpq is nigh useless for testing
purposes, because there's no way to activate that code path on command.
It only runs if libpq (thinks it) is connecting to a pre-7.4 backend.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Successor of MD5 authentication, let's use SCRAM
Next
From: Fabien COELHO
Date:
Subject: Re: review: pgbench progress report improvements