Re: some ri_triggers.c cleanup

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: some ri_triggers.c cleanup
Date: 2019-02-28 19:45:36
Message-ID: 909a8b3f-4b01-2480-d461-a50bf17e55e3@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-02-25 17:17, Corey Huinker wrote:
> Right, this makes a lot of sense, similar to how ri_restrict() combines
> RESTRICT and NO ACTION.
>
>
> I'm pretty sure that's where I got the idea, yes. 

Committed, including your patch.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-02-28 19:55:37 Re: reloption to prevent VACUUM from truncating empty pages at the end of relation
Previous Message Alvaro Herrera 2019-02-28 19:32:03 Re: pg_partition_tree crashes for a non-defined relation