| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump --with-* options |
| Date: | 2025-06-12 21:20:11 |
| Message-ID: | 8f4dc84b52165fa31402259b2ab45ae7a04dff42.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2025-06-12 at 21:16 +0200, Peter Eisentraut wrote:
> > Do we have other options that are order-sensitive?
>
> I think most of them are. For example:
>
> psql -p 5432 -p 5433
> initdb --data-checksums --no-data-checksums
> postgres --shared-buffers=1GB --shared-buffers=2GB
Interesting. I don't think the "last option wins" model applies to
other pg_dump options, though. For instance, in PG17:
pg_dump --data-only --schema-only
pg_dump: error: options -s/--schema-only and -a/--data-only cannot be
used together
I don't think it's simple to start using "last option wins" behavior
now. There are probably some combinations of options where it's not
clear whether a later option is an extra constraint or will override a
previous option.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2025-06-12 22:23:11 | Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin |
| Previous Message | Christoph Berg | 2025-06-12 21:16:19 | Re: pgsql: Introduce pg_shmem_allocations_numa view |