From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adrian Vondendriesch <adrian(dot)vondendriesch(at)credativ(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink |
Date: | 2014-04-19 12:42:07 |
Message-ID: | 20140419124207.GA31555@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 16, 2014 at 11:01:56PM -0400, Bruce Momjian wrote:
> On Tue, Apr 1, 2014 at 10:32:01AM -0400, Tom Lane wrote:
> > Adrian Vondendriesch <adrian(dot)vondendriesch(at)credativ(dot)de> writes:
> > > I patched the function conninfo_array_parse() which is used by
> > > PQconnectStartParams to behave like PQsetdbLogin. The patch also
> > > contains a document patch which clarify "unspecified" parameters.
> >
> > I see no documentation update here. I'm also fairly concerned about the
> > implication that no connection parameter, now or in future, can ever have
> > an empty string as the correct value.
>
> I thought about this. We have never needed PQsetdbLogin() to handle
> zero-length strings specially in all the years we used it, so I am not
> sure why we would ever need PQconnectdbParams() to handle it. I am
> thinking we should make PQconnectdbParams() handle zero-length strings
> the same as NULL, and document it.
>
> Attached is a slightly-modified version of Adrian Vondendriesch's patch.
Patch applied.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2014-04-19 17:10:39 | Re: Docs incorrectly claiming equivalence between show and pg_settings |
Previous Message | Bruce Momjian | 2014-04-19 02:21:08 | Re: pg_upgrade & tablespaces |