Re: pg_dumpall --roles-only interact with other options
| От | Nathan Bossart |
|---|---|
| Тема | Re: pg_dumpall --roles-only interact with other options |
| Дата | |
| Msg-id | aX4sHStDegPd2DzL@nathan обсуждение исходный текст |
| Ответ на | pg_dumpall --roles-only interact with other options (jian he <jian.universality@gmail.com>) |
| Ответы |
Re: pg_dumpall --roles-only interact with other options
|
| Список | 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 по дате отправления: