Trigger which fires on commit? (Multi-table intergrity constraint) - Mailing list pgsql-general

From Stephane Bortzmeyer
Subject Trigger which fires on commit? (Multi-table intergrity constraint)
Date
Msg-id 20020808082241.GA3059@nic.fr
Whole thread Raw
Responses Re: Trigger which fires on commit? (Multi-table intergrity constraint)  (Richard Huxton <dev@archonet.com>)
List pgsql-general
Hello,

[Question already asked but may be badly explained. I rephrase it.]

I have several tables and an integrity constraint which spans several
tables (for an Internet registry, a table Domains, a table Hosts and a
table Nameservers which links them: a Domain needs >= 2
nameservers). The tables are updated in the same transaction and I
want the database to be OK after the commit.

I can check many things from triggers but apparently triggers can only
be fired for a statement (like INSERT), not for a whole transaction.

Oracle supports ON COMMIT triggers and they solve nicely this
problem. But apparently PostgreSQL does not. Any idea?



pgsql-general by date:

Previous
From: "Alex Cheung Tin Ka"
Date:
Subject: "history" key in pgsql
Next
From: Stephane Bortzmeyer
Date:
Subject: Re: "history" key in pgsql