Re: before trigger doesn't, on insert of too long data - Mailing list pgsql-bugs

From Neil Conway
Subject Re: before trigger doesn't, on insert of too long data
Date
Msg-id 8765hryhfm.fsf@mailbox.samurai.com
Whole thread Raw
In response to Re: before trigger doesn't, on insert of too long data  (Gaetano Mendola <mendola@bigfoot.com>)
Responses Re: before trigger doesn't, on insert of too long data  (Gaetano Mendola <mendola@bigfoot.com>)
List pgsql-bugs
Gaetano Mendola <mendola@bigfoot.com> writes:
> I don't know how the check for the data integrity is implemented but if
> is a trigger

It isn't -- trigger firing order is irrelevant to the original
question.

> 1) Create table
> 2) create a before insert trigger:   trigger_a
> 3) create a before insert trigger:   trigger_b
>
> test=# insert into test values ( 10 );
> NOTICE:  TRIGGER A
> NOTICE:  TRIGGER B
> INSERT 3416835 1

The firing order of triggers in PostgreSQL is documented: it is done
alphabetically. When this was discussed, the consensus was that the
"fire by creation order" part of the spec is not very useful, so we
decided to deviate from it deliberately.

-Neil

pgsql-bugs by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: before trigger doesn't, on insert of too long data
Next
From: Gaetano Mendola
Date:
Subject: Re: before trigger doesn't, on insert of too long data