From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | fabriziomello(at)gmail(dot)com |
Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Order of enforcement of CHECK constraints? |
Date: | 2015-03-20 19:37:29 |
Message-ID: | 26615.1426880249@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
=?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= <fabriziomello(at)gmail(dot)com> writes:
> On Fri, Mar 20, 2015 at 4:19 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> On Fri, Mar 20, 2015 at 12:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> We could fix it by, say, having CheckConstraintFetch() sort the
>>> constraints by name after loading them.
>> What not by OID, as with indexes? Are you suggesting that this would
>> become documented behavior?
> I think they should be executed in alphabetical order like triggers.
Yeah. We already have a comparable, and documented, behavior for
triggers, so if we're going to do anything about this I'd vote for
sorting by name (or more specifically, by strcmp()).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Flower | 2015-03-20 19:38:54 | Re: Order of enforcement of CHECK constraints? |
Previous Message | Joshua D. Drake | 2015-03-20 19:29:20 | Re: Remove fsync ON/OFF as a visible option? |