From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Abhijit Menon-Sen <ams(at)toroid(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Wire protocol docs |
Date: | 2009-10-13 16:43:42 |
Message-ID: | 937d27e10910130943o27f8d161n2187683d4f1482dc@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 13, 2009 at 5:41 PM, Abhijit Menon-Sen <ams(at)toroid(dot)org> wrote:
> At 2009-10-13 17:25:15 +0100, dpage(at)pgadmin(dot)org wrote:
>>
>> I cannot find anything that is obviously 'elsewhere' in the docs -
>> does that need fixing, or do my searching skills need improving?
>
> I don't know, but…
>
>> *starts reading source code* :-)
>
> Look at what fe-protocol3.c:build_startup_packet() does with its options
> argument (and see fe-connect.c:EnvironmentOptions to see what is passed
> to it). Basically, libpq sets some connection parameters to values taken
> from the environment (e.g. client_encoding from PGCLIENTENCODING).
Yeah, grep found that pretty quickly :-)
> What
> the documentation you quoted is saying is that the wire protocol doesn't
> know or care where the values came from.
Right. My complaint though, is that the docs imply that the info on
how those values get set is in the docs somewhere, which appears to be
incorrect.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2009-10-13 16:49:13 | Re: Client application name |
Previous Message | Abhijit Menon-Sen | 2009-10-13 16:41:46 | Re: Wire protocol docs |