Prev: transaction_isolation vs.default_transaction_isolation
Next: Reason why set-value functions not allowed in GREATEST(), etc?
From: Bruce Momjian on 22 Feb 2010 13:12
Dave Page wrote:
> On Tue, Oct 13, 2009 at 6:24 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
> > Dave Page <dpage(a)pgadmin.org> writes:
> >> 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.
> >
> > The libpq documentation does cover the fact that libpq uses those
> > variables to establish initial settings. ?I wouldn't expect it to
> > go into implementation details, would you?
>
> Not the libpq docs, no. I was expecting something to though, having
> been told in the intro to the low level protocol details that:
>
> "Higher level features built on this protocol (for example, how libpq
> passes certain environment variables when the connection is
> established) are covered elsewhere."
>
> Note that it says *how* libpq passes those variables which implies the
> mechanism of passing them to the server. Anyway, I can figure out what
> I need from the existing code - I just found that sentence misleading
> and think it should probably be removed.

Agreed, removed.

--
Bruce Momjian <bruce(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: transaction_isolation vs.default_transaction_isolation
Next: Reason why set-value functions not allowed in GREATEST(), etc?