From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, Neil Conway <neilc(at)samurai(dot)com> |
Subject: | Re: before trigger doesn't, on insert of too long data |
Date: | 2003-11-10 22:02:24 |
Message-ID: | 20031110220224.GB27541@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Nov 10, 2003 at 21:48:30 +0100,
Gaetano Mendola <mendola(at)bigfoot(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2003-11-10 22:42:05 | Re: before trigger doesn't, on insert of too long data |
Previous Message | Tom Lane | 2003-11-10 21:09:00 | Re: pg_dumpall does not save CREATE permission on databases |