| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | amul sul <sulamul(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cannot dump foreign key constraints on partitioned table |
| Date: | 2018-07-12 18:45:37 |
| Message-ID: | 20180712184537.5vjwgxlbuiomomqd@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-Jul-12, Michael Paquier wrote:
> Changing pg_class.relhastriggers is out of scope because as far as I
> know partitioned tables have no triggers, so the current value is
> correct, and that would be a catalog change at this stage which would
> cause any existing deployments of v11 to complain about the
> inconsistency. I think that this should be fixed client-side as the
> attached does.
Thanks, looks good. I propose to add following pg_dump test to ensure
this stays fixed.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Dump-foreign-keys-on-partitioned-tables.patch | text/plain | 2.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-07-12 18:52:09 | Re: Cache invalidation after authentication (on-the-fly role creation) |
| Previous Message | Peter Eisentraut | 2018-07-12 18:28:37 | Re: assert in nested SQL procedure call in current HEAD |