From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Foreign keys and partitioned tables |
Date: | 2018-03-31 13:09:01 |
Message-ID: | 8a3e483c-d89f-6872-74ac-5f0ee36357eb@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/29/18 23:19, Alvaro Herrera wrote:
> 0001 prohibits having foreign keys pointing to partitioned tables, as
> discussed above.
This is already prohibited. You get an error
ERROR: cannot reference partitioned table "fk_partitioned_pk"
Your patch 0001 just adds the same error check a few lines above the
existing one, while 0003 removes the existing one.
I think you can squash 0001 and 0003 together.
> 0002 is a fixup for a bug in the row triggers patch: I had a restriction
> earlier that triggers declared internal were not cloned, and I seem to
> have lost it in rebase. Reinstate it.
Hmm, doesn't cause any test changes?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2018-03-31 13:21:04 | Re: hot_standby_feedback vs excludeVacuum and snapshots |
Previous Message | Amit Kapila | 2018-03-31 13:04:15 | Re: [HACKERS][PATCH] adding simple sock check for windows |