Re: Referential Integrity Checks with Statement-level Triggers - Mailing list pgsql-hackers

From Adam Brusselback
Subject Re: Referential Integrity Checks with Statement-level Triggers
Date
Msg-id CAMjNa7fPEUonQJDE2bY4KvCR+Ai7qUTT1XdUhgHYXJ8DMpx+tg@mail.gmail.com
Whole thread Raw
In response to Re: Referential Integrity Checks with Statement-level Triggers  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Referential Integrity Checks with Statement-level Triggers  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: Referential Integrity Checks with Statement-level Triggers  (Emre Hasegeli <emre@hasegeli.com>)
List 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

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: psql exit status with multiple -c or -f
Next
From: Pavel Stehule
Date:
Subject: Re: Referential Integrity Checks with Statement-level Triggers