From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: ewjoachim@gmail.com
Subject: BUG #16206: Documentation for PGDATABASE libpq env var is misleading
Date: Wed, 15 Jan 2020 08:35:08 +0000
Message-ID: <16206-92ff1acf0650ff10@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16206
Logged by: Joachim Jablon
Email address: ewjoachim@gmail.com
PostgreSQL version: 12.1
Operating system: All
Description:
Documentation for PGDATABASE says:
> PGDATABASE behaves the same as the dbname connection parameter.
Documentation for dbname says:
> The database name. Defaults to be the same as the user name. In certain
contexts, the value is checked for extended formats; see Section 33.1.1 for
more details on those.
But PGDATABASE is not checked for extended formats. This should be
explicitly said in the documentation. I believe a simple sentence like:
> PGDATABASE behaves the same as the dbname connection parameter but the
value is not checked for extended format.
might be enough.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, ewjoachim@gmail.com
Subject: Re: BUG #16206: Documentation for PGDATABASE libpq env var is misleading
In-Reply-To: <16206-92ff1acf0650ff10@postgresql.org>
References: <16206-92ff1acf0650ff10@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox