| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: PQconninfoParse() |
| Date: | 2011-10-19 00:27:47 |
| Message-ID: | 28823.1318984067@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, Oct 15, 2011 at 11:24 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Uh, is that actually a true statement? I thought the result *did*
>> include default values. That's more or less the point of returning them
>> all, after all.
> Well, then I'm confused, because you and Dmitriy seem to be saying
> opposite things.
[ after experimenting with the code ... ] Oh, I had been thinking that
PQconndefaults gives the same result as PQconninfoParse with an
empty-string argument, but that's not the case. Indeed, the former
fills in default values as current values, but the latter does not.
The proposed wording change seems reasonable, except that "have a
corresponding value" seems a bit vague. Maybe better "have a non-null
val field".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fred Cox | 2011-10-19 19:04:25 | Algorithm for generating md5 encrypted password not found in documentation |
| Previous Message | Robert Haas | 2011-10-19 00:15:13 | Re: description of CHECKPOINT command confusing |