pgsql: Improve comments about why SET DEFAULT triggers must recheck for

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve comments about why SET DEFAULT triggers must recheck for
Date: 2012-06-19 02:46:03
Message-ID: E1SgoSB-0000ds-11@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Improve comments about why SET DEFAULT triggers must recheck for matches.

I was confused about this, so try to make it clearer for the next person.

(This seems like a fairly inefficient way of dealing with a corner case,
but I don't have a better idea offhand. Maybe if there were a way to turn
off the RI_FKey_keyequal_upd_fk event filter temporarily?)

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/48756be9cf31c37a936eecff051bf143d5866551

Modified Files
--------------
src/backend/utils/adt/ri_triggers.c | 32 ++++++++++++++++++++------------
1 files changed, 20 insertions(+), 12 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-06-19 18:32:04 pgsql: Share RI trigger code between NO ACTION and RESTRICT cases.
Previous Message Tom Lane 2012-06-18 23:37:34 pgsql: Allow ON UPDATE/DELETE SET DEFAULT plans to be cached.