Re: enable/disable broken for statement triggers on partitioned tables

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
Subject: Re: enable/disable broken for statement triggers on partitioned tables
Date: 2022-08-05 10:44:00
Message-ID: CA+HiwqFdv7QK-5v_57jByeH=ymKg-bjC9sXR++uSi5YZqGdtog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 5, 2022 at 6:58 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> OK, pushed. This soon caused buildfarm to show a failure due to
> underspecified ORDER BY, so I just pushed a fix for that too.

Thank you.

--
Thanks, Amit Langote
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2022-08-05 10:48:33 Re: [PATCH] Expose port->authn_id to extensions and triggers
Previous Message Bharath Rupireddy 2022-08-05 10:25:26 Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes?