Re: Referential Integrity Checks with Statement-level Triggers

Поиск
Список
Период
Сортировка
От Adam Brusselback
Тема Re: Referential Integrity Checks with Statement-level Triggers
Дата
Msg-id CAMjNa7fPEUonQJDE2bY4KvCR+Ai7qUTT1XdUhgHYXJ8DMpx+tg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Referential Integrity Checks with Statement-level Triggers  (Pavel Stehule <pavel.stehule@gmail.com>)
Ответы 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>)
Список 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 по дате отправления:

Предыдущее
От: Justin Pryzby
Дата:
Сообщение: psql exit status with multiple -c or -f
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: Referential Integrity Checks with Statement-level Triggers