Re: Listing triggers in partitions (was Re: Remove mention in docsthat foreign keys on partitioned tables) - Mailing list pgsql-hackers

From David Rowley
Subject Re: Listing triggers in partitions (was Re: Remove mention in docsthat foreign keys on partitioned tables)
Date
Msg-id CAKJS1f9H56xnnh=mpBcBNd3G2fnndqftbVq6NuL9aOHFwkV4hw@mail.gmail.com
Whole thread Raw
In response to Listing triggers in partitions (was Re: Remove mention in docs thatforeign keys on partitioned tables)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Listing triggers in partitions (was Re: Remove mention in docsthat foreign keys on partitioned tables)
List pgsql-hackers
On 28 June 2018 at 09:01, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> Another angle is that we're already in beta3 and there may be concerns
> about altering catalog definition this late in the cycle.  Anybody?
> Maybe psql can just match tgisinternal triggers by name, and if one
> match occurs then we assume it's a clone that should be listed as a
> partition trigger.

Are catversion bumps really a huge problem in beta?  Looks like there
were quite a few during the v10 cycle.

$ git log REL_10_BETA2..REL_10_BETA3 --oneline --
src\include\catalog\catversion.h | wc -l
      1

$ git log REL_10_BETA1..REL_10_BETA2 --oneline --
src\include\catalog\catversion.h | wc -l
      9

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Capitalization of the name OpenSSL
Next
From: Alvaro Herrera
Date:
Subject: Re: Listing triggers in partitions (was Re: Remove mention in docsthat foreign keys on partitioned tables)