From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | christophe(dot)courtois(at)dalibo(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgbench: supports PGDATABASE / warning about -d |
Date: | 2021-02-24 05:29:31 |
Message-ID: | YDXkO0HXIwh9ROkD@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Mon, Feb 22, 2021 at 11:39:46AM +0000, PG Doc comments form wrote:
> 1) pgbench has always supported the PGDATABASE env variable, but it is not
> listed along PGHOST/PGPORT & PGUSER in
> https://www.postgresql.org/docs/13/pgbench.html#id-1.9.4.10.8.
> PGDATABASE is listed in the pages of the psql/pg_dump/createdb...
> utilities
Yeah, let's fix that. Adding only PGDATABASE to the list of
environment variables supported does not look enough to me, so I
propose the simple patch attached to clarify what happens to dbname in
more details.
> 2) In "Common options", it would be useful to add a warning that "-d means
> --debug and does NOT define the database, contrary to most other PostgreSQL
> utilities".
> (It seems to work and the consequence is a flood of SQL orders on the
> screen.)
I don't agree with this part.
--
Michael
Attachment | Content-Type | Size |
---|---|---|
pgbench-doc-db.patch | text/x-diff | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-02-24 05:49:14 | Re: incoorect restore_command |
Previous Message | Michael Paquier | 2021-02-24 02:19:41 | Re: Inaccuracy in wal_receiver_status_interval parameter description |