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

From Alvaro Herrera
Subject Re: Remove mention in docs that foreign keys on partitioned tablesare not supported
Date
Msg-id 20180627191819.6g73wu7ck23fdhv6@alvherre.pgsql
Whole thread Raw
In response to Re: Remove mention in docs that foreign keys on partitioned tablesare not supported  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Listing triggers in partitions (was Re: Remove mention in docs thatforeign keys on partitioned tables)
List pgsql-hackers
On 2018-Jun-19, Amit Langote wrote:

> In CreateTrigger(), 86f575948c7 did this.
> 
> -    values[Anum_pg_trigger_tgisinternal - 1] = BoolGetDatum(isInternal);
> +    values[Anum_pg_trigger_tgisinternal - 1] = BoolGetDatum(isInternal ||
> in_partition);
> 
> I'm not sure why it had to be done, but undoing this change doesn't seem
> to break any regression tests (neither those added by 86f575948c7 nor of
> the partitioned table foreign key commit).  Did we really intend to change
> the meaning of tginternal like this here?

I'm pretty sure pg_dump breaks if you turn that flag off for triggers in
partitions, because pg_dump is going to emit commands to create those
triggers, and those fail.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Allow cancelling VACUUM of nbtrees with corrupted right links
Next
From: Andres Freund
Date:
Subject: Re: Allow cancelling VACUUM of nbtrees with corrupted right links