Re: Remove mention in docs that foreign keys on partitioned tables are not supported - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Remove mention in docs that foreign keys on partitioned tables are not supported
Date
Msg-id 8501.1528145405@sss.pgh.pa.us
Whole thread Raw
In response to Re: Remove mention in docs that foreign keys on partitioned tablesare not supported  (Robert Haas <robertmhaas@gmail.com>)
Responses 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
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jun 4, 2018 at 1:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.)

> That seems like a somewhat-unfortunate restriction.

Perhaps, but I'm having a hard time wrapping my mind around what the
semantics ought to be.  If a trigger on partition A changes the keys
so that the row shouldn't have gone into A at all, what then?  That
trigger should never have fired, eh?

            regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Remove mention in docs that foreign keys on partitioned tablesare not supported
Next
From: Robert Haas
Date:
Subject: Re: Loaded footgun open_datasync on Windows