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

From Bruno Wolff III
Subject Re: before trigger doesn't, on insert of too long data
Date
Msg-id 20031110220224.GB27541@wolff.to
Whole thread Raw
In response to Re: before trigger doesn't, on insert of too long data  (Gaetano Mendola <mendola@bigfoot.com>)
List pgsql-bugs
On Mon, Nov 10, 2003 at 21:48:30 +0100,
  Gaetano Mendola <mendola@bigfoot.com> wrote:
> Seems to me too, from the standard:
>
> "The order of execution of a set of triggers is ascending by value of
> their timestamp of creation in their
> descriptors, such that the oldest trigger executes first. If one or more
> triggers have the same timestamp value,
> then their relative order of execution is implementation-defined."

I don't think Postgres uses that ordering. My memory is that it is based
on the collation order of the trigger name because that allowed better
control of trigger firing order.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dumpall does not save CREATE permission on databases
Next
From: Neil Conway
Date:
Subject: Re: before trigger doesn't, on insert of too long data