Magnus Hagander wrote:
> Tom Lane wrote:
> > Magnus Hagander writes:
> >> Any reason not to just have the environment variable documentation refer
> >> back to the connection option documentation?
> >
> > Well, not all of 'em are connection options.
> >
> > I could see documenting the connection
Magnus Hagander wrote:
> Well, I was mostly thinking like:
> PGSSLMODE
> This corresponds to the sslmode connection option.
>
> Then for those that aren't connection options, we'd keep the full
> description. I'm not advocating we remove the whole chapter, just the
> duplicated stuff. (I assume
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Any reason not to just have the environment variable documentation refer
>> back to the connection option documentation?
>
> Well, not all of 'em are connection options.
>
> I could see documenting the connection options more like t
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Any reason not to just have the environment variable documentation refer
> back to the connection option documentation?
Well, not all of 'em are connection options.
I could see documenting the connection options more like the
GUC-variable options, ie
There seems to be a lot of duplication in the libpq documentation
between the connection string parameters and the environment variables.
They are close to identical but not exactly (for example, there is a
"and vs or" change in PGSSLMODE/sslmode).
Any reason not to just have the environment varia
