Re: pg_dump versus hash partitioning - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_dump versus hash partitioning
Date
Msg-id CA+TgmobF7EwMQ0bR3ZPKdtuVa7jkixWQpm3AX6jwv6YD041EFw@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump versus hash partitioning  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump versus hash partitioning
List pgsql-hackers
On Mon, Feb 27, 2023 at 11:20 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Well, that's a user error not pg_dump's fault.  Particularly so for hash
> partitioning, where there is no defensible reason to make the partitions
> semantically different.

I am still of the opinion that you're going down a dangerous path of
redefining pg_dump's mission from "dump and restore the database, as
it actually exists" to "dump and restore the database, unless the user
did something that I think is silly".

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Stale references to guc.c in comments/tests
Next
From: John Naylor
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum