| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, wangpeng <215722532(at)qq(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dumpall --roles-only interact with other options |
| Date: | 2026-02-06 09:36:43 |
| Message-ID: | CAN4CZFMbSpaEZNGCAo-ky93OQPYBvbsTS1bNdF8d91HtLKrdEQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello!
> I believe "schema" generally refers to object definitions, excluding
> things like roles and tablespaces.
Please see the attached tap test case. It works with the current
master branch, and fails with the patch. Basically my expectation is
that if we use dumpall --schema-only, we should be able to restore it
without errors, except for one error for the already existing
postgres/current user which it ignores.
I also found one more issue/behavior change: --no-schema --clean now
generates DROP statements (roles, tablespaces, databases), while
previously it didn't.
| Attachment | Content-Type | Size |
|---|---|---|
| 007_schema_only_roles.pl | application/octet-stream | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-02-06 09:40:02 | Re: client_connection_check_interval default value |
| Previous Message | Bowen Shi | 2026-02-06 09:25:56 | Re: Changing shared_buffers without restart |