On 12/11/19 9:06 AM, Tom Lane wrote:
Adrian Klaver writes:
On 12/11/19 5:18 AM, Олег Самойлов wrote:
This utility, like most other PostgreSQL utilities, also uses the environment
variables supported by libpq (see Section 33.14).
https://www.postgresql.org/docs/12/libpq-envars.html
PGUSER behav
Adrian Klaver writes:
> On 12/11/19 5:18 AM, Олег Самойлов wrote:
> This utility, like most other PostgreSQL utilities, also uses the environment
> variables supported by libpq (see Section 33.14).
> https://www.postgresql.org/docs/12/libpq-envars.html
> PGUSER behaves the same as the user connec
On 12/11/19 5:18 AM, Олег Самойлов wrote:
This utility, like most other PostgreSQL utilities, also uses the environment
variables supported by libpq (see Section 33.14).
"
https://www.postgresql.org/docs/12/libpq-envars.html
"
PGUSER behaves the same as the user connection parameter.
"
This
> This utility, like most other PostgreSQL utilities, also uses the environment
> variables supported by libpq (see Section 33.14).
> "
>
> https://www.postgresql.org/docs/12/libpq-envars.html
> "
> PGUSER behaves the same as the user connection parameter.
> "
This is don't work with `initdb`
On 12/10/19 5:21 AM, Олег Самойлов wrote:
PGUSER doesn't work with initdb and pg_ctl initdb. Lets explain, where this can
be important. For instance in MacOS the most convenient way to manage
PostgresQL is homebrew.
To install PostgresQL:
brew install postgresql
To upgrade:
brew upgrade pos
PGUSER doesn't work with initdb and pg_ctl initdb. Lets explain, where this can
be important. For instance in MacOS the most convenient way to manage
PostgresQL is homebrew.
To install PostgresQL:
brew install postgresql
To upgrade:
brew upgrade postgresql
this will upgrade soft and to upgr
