Re: pg_dumpall --roles-only interact with other options - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: pg_dumpall --roles-only interact with other options
Date
Msg-id aX4sHStDegPd2DzL@nathan
Whole thread Raw
In response to pg_dumpall --roles-only interact with other options  (jian he <jian.universality@gmail.com>)
List pgsql-hackers
On Sat, Jan 31, 2026 at 11:50:50AM +0800, jian he wrote:
> pg_dumpall --verbose --roles-only --no-schema --file=1.sql
> pg_dumpall --verbose --roles-only --no-data --file=2.sql
> pg_dumpall --verbose --roles-only --no-statistics --file=3.sql

These seem permissible to me.  The --no-* options are redundant, but the
user intent seems clear.

> pg_dumpall --verbose --roles-only --statistics-only --file=4.sql
> pg_dumpall --verbose --roles-only --data-only --file=5.sql
> pg_dumpall --verbose --roles-only --schema-only --file=6.sql
>
> [...]
>
> This situation also happens to another pg_duampall option:
> --tablespaces-only.

Yeah, conflicting --*-only options should probably cause errors, like we do
for pg_dump.

-- 
nathan



pgsql-hackers by date:

Previous
From: KAZAR Ayoub
Date:
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD
Next
From: Florents Tselai
Date:
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part