Re: pg_dumpall --roles-only interact with other options

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dumpall --roles-only interact with other options
Date: 2026-01-31 16:21:49
Message-ID: aX4sHStDegPd2DzL@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Florents Tselai 2026-01-31 16:23:27 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Previous Message KAZAR Ayoub 2026-01-31 16:20:58 Re: Speed up COPY FROM text/CSV parsing using SIMD