From: | Adrian Vondendriesch <adrian(dot)vondendriesch(at)credativ(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-01 15:06:08 |
Message-ID: | 533AD5E0.1030807@credativ.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg토토 사이트 추천SQL |
Am 01.04.2014 16:32, schrieb Tom Lane:
> 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.
If we want to preserve the possibility to except an empty string as
correct value, then pgbench should initialise some variables with
NULL instead of empty string.
Moreover it should be documented that "unspecified" means NULL and not
empty string, like in PQsetdbLogin.
However, attached you will find the whole patch, including documentation.
Kind Regards
- Adrian
Attachment | Content-Type | Size |
---|---|---|
libpq_conninfo_array_parse_empty_string_v1.patch | text/x-patch | 1.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-04-01 15:13:30 | Re: BUG #9518: temporary login failure - "missing pg_hba entry" |
Previous Message | Andres Freund | 2014-04-01 14:59:26 | Re: Including replication slot data in base backups |