Re: Referential Integrity Checks with Statement-level Triggers

From: Emre Hasegeli <emre(at)hasegeli(dot)com>
To: Adam Brusselback <adambrusselback(at)gmail(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Referential Integrity Checks with Statement-level Triggers
Date: 2018-12-22 16:28:13
Message-ID: CAE2gYzxGYagVfHvG9bMAiz7vjGK7GQwVaY0YLddPditD1o6kcQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.

Me too. Never-ending DELETEs are a common pain point especially for
people migrated from MySQL which creates indexes for foreign keys
automatically.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-12-22 16:31:20 Re: Joins on TID
Previous Message Michael Banck 2018-12-22 13:42:55 Re: Offline enabling/disabling of data checksums