| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | ewjoachim(at)gmail(dot)com |
| Subject: | BUG #16206: Documentation for PGDATABASE libpq env var is misleading |
| Date: | 2020-01-15 08:35:08 |
| Message-ID: | 16206-92ff1acf0650ff10@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16206
Logged by: Joachim Jablon
Email address: ewjoachim(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | andreas | 2020-01-15 09:46:50 | create rule with multiple commands |
| Previous Message | Michael Paquier | 2020-01-15 05:14:18 | Re: libpq parameter parsing problem |