Re: pg_restore error with partitioned table having exclude constraint

From: Japin Li <japinli(at)hotmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Keith Paskett <keith(dot)paskett(at)logansw(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: pg_restore error with partitioned table having exclude constraint
Date: 2025-04-30 06:38:14
Message-ID: ME0P300MB0445A5BF45A46CC72B39C580B6832@ME0P300MB0445.AUSP300.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 29 Apr 2025 at 16:53, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> On 2025-Apr-29, Japin Li wrote:
>
>> My understanding, based on the src/bin/pg_dump tests, is that they don't
>> involve a genuine restore of the dumped data to a database. Instead, it
>> dumps to a file using pg_restore. Is that correct?
>
> Yes.
>
>> I doubt whether I can add a test to pg_dump that would cover this issue.
>
> The pg_upgrade now includes a roundtrip dump/restore which you can take
> advantage of. You just need to ensure some of the src/test/regress/sql
> files leave an object in the state you need, and the pg_upgrade test
> will run those tests and try to dump and restore the resulting database.
>

Thank you for the explanation. A test case has been added to create_index.sql.
Could you please take a look?

--
Regrads,
Japin Li

Attachment Content-Type Size
restore-partitioned-tables-with-exclude-constraints.patch text/x-diff 2.3 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Álvaro Herrera 2025-04-30 10:45:11 Re: pg_restore error with partitioned table having exclude constraint
Previous Message Jacob Champion 2025-04-29 18:48:01 Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq