| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Allow FOR EACH ROW triggers on partitioned tables |
| Date: | 2018-03-25 05:01:45 |
| Message-ID: | 20180325050145.exr5xfnihpj3dly5@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Hi,
On 2018-03-23 13:48:53 +0000, Alvaro Herrera wrote:
> Allow FOR EACH ROW triggers on partitioned tables
>
> Previously, FOR EACH ROW triggers were not allowed in partitioned
> tables. Now we allow AFTER triggers on them, and on trigger creation we
> cascade to create an identical trigger in each partition. We also clone
> the triggers to each partition that is created or attached later.
>
> This means that deferred unique keys are allowed on partitioned tables,
> too.
>
> Author: Álvaro Herrera
> Reviewed-by: Peter Eisentraut, Simon Riggs, Amit Langote, Robert Haas,
> Thomas Munro
> Discussion: https://postgr.es/m/20171229225319.ajltgss2ojkfd3kp@alvherre.pgsql
The inherit.sql here looks like it's racing against the concurrentlys
scheduled triggers.sql according to my new desmoxytes animal:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=desmoxytes&dt=2018-03-25%2004%3A48%3A01
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-03-25 13:10:43 | pgsql: pg_resetwal: Fix logical typo in code |
| Previous Message | Tom Lane | 2018-03-25 04:47:33 | Re: pgsql: Add long options to pg_resetwal and pg_controldata |