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

From Alex
Subject Re: Inconsistency in libpq connection parameters, and extension thereof
Date
Msg-id 87txyhpt0c.fsf@commandprompt.com
Whole thread Raw
In response to Re: Inconsistency in libpq connection parameters, and extension thereof  (Daniel Farina <daniel@heroku.com>)
List pgsql-hackers
Daniel Farina <daniel@heroku.com> writes:

> On Tue, Jun 5, 2012 at 6:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>
>> Um.  We oughta fix that.  I'm not necessarily wedded to the old
>> throw-an-error definition, but there seems no good reason for these
>> two syntaxes to act inconsistently.
>
> I agree with that.  The URIs may have been done this way as a
> concession to some small fragmentation that may have taken place
> before URIs were standardized, but perhaps the author can speak to
> that (he has been put on the To: list for this mail).

Sorry for the silence.

The original intent was to not error out on any extra parameters from
JDBC or other existing URI implementations.  The example of a possible
typo in sslmode=require clearly demonstrates that this was not
a well-thought decision.

Anyway, I can see you've already sorted this out.

--
Alex


pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Restrict ALTER FUNCTION CALLED ON NULL INPUT (was Re: Not quite a security hole: CREATE LANGUAGE for non-superusers)
Next
From: Bruce Momjian
Date:
Subject: Re: [COMMITTERS] pgsql: Run pgindent on 9.2 source tree in preparation for first 9.3