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

From Corey Huinker
Subject Re: some ri_triggers.c cleanup
Date
Msg-id CADkLM=fwEQ+PL9iV3cGoPrUbFkyF0ArhRVoBeOsJ6fXmKt0qSw@mail.gmail.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
List pgsql-hackers
On Fri, Feb 22, 2019 at 1:12 PM Corey Huinker <corey.huinker@gmail.com> wrote:
On Fri, Feb 22, 2019 at 11:05 AM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
ri_triggers.c is endlessly long and repetitive.  I want to clean it up a
bit (more).

Having just been down this road, I agree that a lot of cleanup is needed and possible.
 
I looked into all these switch cases for the unimplemented MATCH PARTIAL
option.  I toyed around with how a MATCH PARTIAL implementation would
actually look like, and it likely wouldn't use the existing code
structure anyway, so let's just simplify this for now.

+1

 
Attached are some patches.

I intend to look this over in much greater detail, but I did skim the code and it seems like you left the SET DEFAULT and SET NULL paths separate. In my attempt at statement level triggers I realized that they only differed by the one literal value, and parameterized the function.
 

I've looked it over more closely now and I think that it's a nice improvement.

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).

Passes make check. 
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Autovaccuum vs temp tables crash
Next
From: Corey Huinker
Date:
Subject: Re: \describe*