Re: Inconsistency in libpq connection parameters, and extension thereof - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Inconsistency in libpq connection parameters, and extension thereof
Date
Msg-id 5692.1338955369@sss.pgh.pa.us
Whole thread Raw
In response to Re: Inconsistency in libpq connection parameters, and extension thereof  (Daniel Farina <daniel@heroku.com>)
Responses Re: Inconsistency in libpq connection parameters, and extension thereof  (Daniel Farina <daniel@heroku.com>)
List pgsql-hackers
Daniel Farina <daniel@heroku.com> writes:
> Would these hypothetical extension-pairs be using the "options" device
> at startup time, or something else (possibly brand new)?

I'd argue for just translating them into "options", at least in the
near term.  If they use some new mechanism then they would only work
with new servers, and it's generally not good for libpq to assume much
about what version of server it's working with, especially not when
sending an initial connection packet (when, by definition, it can't
know that for sure).

As far as changing such settings later in the session is concerned,
isn't that what SET is for?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: Re: Inconsistency in libpq connection parameters, and extension thereof
Next
From: Daniel Farina
Date:
Subject: Re: Inconsistency in libpq connection parameters, and extension thereof