| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Japin Li <japinli(at)hotmail(dot)com> |
| 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-29 14:53:52 |
| Message-ID: | 202504291453.r37jvblkfqcu@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Debido a que la velocidad de la luz es mucho mayor que la del sonido,
algunas personas nos parecen brillantes un minuto antes
de escuchar las pelotudeces que dicen." (Roberto Fontanarrosa)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2025-04-29 16:35:36 | BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq |
| Previous Message | Japin Li | 2025-04-29 14:44:16 | Re: pg_restore error with partitioned table having exclude constraint |