The option was not described: connection-option

Also I have issue with this command:

pg_dump -d 'postgresql://postgres@host.internal?sslmode=require' --create
--clean --if-exists mydb
pg_dump: error: too many command-line arguments (first is "userdb")
pg_dump: hint: Try "pg_dump --help" for more information.

I want to connect to 'postgres' database and dump 'mydb', because database
was turned to readonly mode and does not accept connections:

pg_dump -d 'postgresql://postgres@host.internal/userdb?sslmode=require'
--create --clean --if-exists
pg_dump: error: connection to server at "host.internal" (172.31.x.x), port
5432 failed: FATAL: database "mydb" is not currently accepting connections

Please note, this is not the question and I am not looking for help. Here I
want to share my use case which is not covered in doc. Eg `-d XXX` option
with `dbname` parameter.

On Thu, Sep 19, 2024 at 12:47 PM PG Doc comments form <
noreply@postgresql.org> wrote:

On Thu, Sep 19, 2024 at 10:31 AM PG Doc comments form <
noreply@postgresql.org> wrote:

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/16/app-pgdump.html
Description:

Hi.

The option `connection-option` is mentioned but is not described.

Please describe it.

They are described though the terminology is a bit inconsistent:

<command> also accepts the following command-line arguments for connection
parameters:

The items listed beneath that sentence fragment are the connection-options.

If someone wants to go, IMO, busy-fix all of the pages that use the above
wording to better align with the synopsis I won't argue. But it's low on
my priority list.

David J.

On Thu, Sep 19, 2024 at 10:31 AM Eugen Konkov <konkove@gmail.com> wrote:

I want to connect to 'postgres' database and dump 'mydb', because database
was turned to readonly mode and does not accept connections:

This is fundamentally impossible by the design of the system. You can only
dump the database you connect to.

David J.