Re: BUG #15499: pg_dump does not read connection URL from environment variable
| От | David G. Johnston |
|---|---|
| Тема | Re: BUG #15499: pg_dump does not read connection URL from environment variable |
| Дата | |
| Msg-id | CAKFQuwbjbpj0Rjdzmc3BFRqA6P2fngtoXNrUFUybp4J7NQtRNA@mail.gmail.com обсуждение исходный текст |
| Ответ на | BUG #15499: pg_dump does not read connection URL from environmentvariable (PG Bug reporting form <noreply@postgresql.org>) |
| Ответы |
Re: BUG #15499: pg_dump does not read connection URL from environment variable
|
| Список | pgsql-bugs |
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.
В списке pgsql-bugs по дате отправления: