Re: Remove mention in docs that foreign keys on partitioned tables are not supported
| От | Tom Lane |
|---|---|
| Тема | Re: Remove mention in docs that foreign keys on partitioned tables are not supported |
| Дата | |
| Msg-id | 32486.1528134158@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Remove mention in docs that foreign keys on partitioned tablesare not supported (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: Remove mention in docs that foreign keys on partitioned tablesare not supported
Re: Remove mention in docs that foreign keys on partitioned tablesare not supported |
| Список | pgsql-hackers |
Alvaro Herrera <alvherre@2ndquadrant.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
В списке pgsql-hackers по дате отправления: