Thread: BUG #15499: pg_dump does not read connection URL from environmentvariable
BUG #15499: pg_dump does not read connection URL from environmentvariable
From
PG Bug reporting form
Date:
The following bug has been logged on the website: Bug reference: 15499 Logged by: Yonatan Romero Email address: yromero@onapsis.com PostgreSQL version: Unsupported/Unknown Operating system: Ubuntu 14.04 LTS Description: pg_dump's docs says this command can use connection string on --dbname argument[1]. Also, the libpq environments variables's documentation says PGDATABASE behaves the same as the dbname connection parameter[2]. I try to pass connection string on PGDATABASE environment variable, but it does work. yromero@onapsis:~$ env PGDATABASE="postgresql://onapsis:secret@localhost/onapsis" pg_dump pg_dump: [archiver (db)] connection to database "postgresql://onapsis:secret@localhost/onapsis" failed: FATAL: role "yromero" does not exist References: [1] https://www.postgresql.org/docs/9.3/app-pgrestore.html [2] https://www.postgresql.org/docs/9.3/libpq-envars.html
Re: BUG #15499: pg_dump does not read connection URL from environment variable
From
"David G. Johnston"
Date:
On Monday, November 12, 2018, PG Bug reporting form <noreply@postgresql.org> wrote:
pg_dump's docs says this command can use connection string on --dbname
argument[1].
A command line argument and the parameter it links to are two separate things.
Also, the libpq environments variables's documentation says PGDATABASE
behaves the same as the dbname connection parameter[2].
Which the linked portion then says:
"In certain contexts, the value is checked for extended formats;"
I try to pass connection string on PGDATABASE environment variable, but it
does [not] work.
Which implies that PGDATABASE envvar interpretation is not one of those places where the extended URI connection string format can be passed; instead the environment variables covering the different parts need to be used. Using them works one-to-one with the plain meaning of the parameters they link to.
Probably the docs could use a note to that effect.
David J.
Re: BUG #15499: pg_dump does not read connection URL from environment variable
From
"Romero, Yonatan"
Date:
Thanks for your time.
Regards
On Mon, Nov 12, 2018 at 6:03 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Monday, November 12, 2018, PG Bug reporting form <noreply@postgresql.org> wrote:pg_dump's docs says this command can use connection string on --dbname
argument[1].A command line argument and the parameter it links to are two separate things.Also, the libpq environments variables's documentation says PGDATABASE
behaves the same as the dbname connection parameter[2].Which the linked portion then says:"In certain contexts, the value is checked for extended formats;"I try to pass connection string on PGDATABASE environment variable, but it
does [not] work.Which implies that PGDATABASE envvar interpretation is not one of those places where the extended URI connection string format can be passed; instead the environment variables covering the different parts need to be used. Using them works one-to-one with the plain meaning of the parameters they link to.Probably the docs could use a note to that effect.David J.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.