| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Remove mention in docs that foreign keys on partitioned tables are not supported |
| Date: | 2018-06-04 17:42:38 |
| Message-ID: | 32486.1528134158@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2018-Jun-04, Tom Lane wrote:
>> ... why doesn't the same problem apply to AFTER triggers that are attached
>> to the inheritance parent?
> With a BEFORE trigger, running the trigger might change the target
> partition, which has the potential for all kinds of trouble.
Got it. That seems like not just an implementation restriction, but
a pretty fundamental issue.
Could we solve it by saying that triggers on partitioned tables aren't
allowed to change the partitioning values? (Or at least, not allowed
to change them in a way that changes the target partition.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Finnerty, Jim | 2018-06-04 18:37:02 | Re: New committers announced at PGCon 2018 |
| Previous Message | Justin Pryzby | 2018-06-04 17:34:10 | Re: \d t: ERROR: XX000: cache lookup failed for relation |