|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>|
|Subject:||Re: deferrable triggers|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> In a discussion on irc today, someone had a need to confirm that a
> business rule (this table has two rows for every related one row in
> another table) was true at commit time. I innocently suggested a
> deferrable (and deferred) trigger. It was pointed out that the
> | This can only be specified for constraint triggers.
> Hmm. Somehow I had gotten hold of deferrable triggers as a way to
> solve a problem in moving our replication from our Java framework to
> PostgreSQL triggers. So we are using a hand-written DEFERRABLE
> trigger in production, with it apparently working as intended.
What do you mean by "hand-written DEFERRABLE trigger"? AFAICS from the
grammar, DEFERRABLE and related attributes can only be specified when
you write CREATE CONSTRAINT TRIGGER, so the documentation's statement
appears correct to me.
regards, tom lane
|Next Message||Tom Lane||2011-12-20 21:24:29||Re: sorting table columns|
|Previous Message||Alvaro Herrera||2011-12-20 20:53:34||sorting table columns|