Re: Referential Integrity Checks with Statement-level Triggers

Adam Brusselback <adambrusselback@gmail.com>

From: Adam Brusselback <adambrusselback@gmail.com>

To: Pavel Stehule <pavel.stehule@gmail.com>

Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Corey Huinker <corey.huinker@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2018-12-17T18:18:56Z

Lists: pgsql-hackers

It's something I know I am interested in. For me, I don't really care if my
statement doesn't cancel until the very end if there is a RI violation. The
benefit of not having deletes be slow on tables which have others
referencing it  with a fkey which don't have their own index is huge IMO. I
have a good number of those type of logging tables where an index is not
useful 99% of the time, but every once and a while a bulk delete needs to
happen.

It is far from a premature optimization IMO, it is super useful and
something I was hoping would happen ever since I heard about transition
tables being worked on.

Just my $0.02.
-Adam