Re: some ri_triggers.c cleanup - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: some ri_triggers.c cleanup
Date
Msg-id 56d791ef-d2c7-f64e-3c62-8ebf1efc7cc6@2ndquadrant.com
Whole thread Raw
In response to Re: some ri_triggers.c cleanup  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: some ri_triggers.c cleanup  (Corey Huinker <corey.huinker@gmail.com>)
List pgsql-hackers
On 2019-02-24 00:34, Corey Huinker wrote:
> As I suspected, the code for SET NULL and SET DEFAULT are highly similar
> (see .diff), the major difference being two constants, the order of some
> variable declarations, and the recheck in the set-default case.
> 
> The changes were so simple that I felt remiss not adding the patch for
> you (see .patch).

Right, this makes a lot of sense, similar to how ri_restrict() combines
RESTRICT and NO ACTION.

I'll take a closer look at your patch.

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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: unconstify equivalent for volatile
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: RE: Protect syscache from bloating with negative cache entries