Re: Referential Integrity Checks with Statement-level Triggers

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Referential Integrity Checks with Statement-level Triggers
Date: 2018-12-17 22:54:06
Message-ID: CACjxUsOY-CXoNMPit+k1PC_5LjYkvYPz2VJwK5YDDtzRh4J7vw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 17, 2018 at 8:32 AM Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:

> All suggestions are appreciated.

As I recall, the main issue is how to handle concurrency. The
existing RI triggers do some very special handling of the multi-xact
ID to manage concurrent modifications. Has anyone looked at the
issues with using those techniques with set-oriented statements for
the transition table approach?

--
Kevin Grittner
VMware vCenter Server
https://www.vmware.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-12-17 23:00:36 Re: 'infinity'::Interval should be added
Previous Message Kevin Grittner 2018-12-17 22:51:19 Re: Referential Integrity Checks with Statement-level Triggers