| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Order of enforcement of CHECK constraints? |
| Date: | 2015-03-20 19:24:01 |
| Message-ID: | CAFcNs+pR7tnJ5_gL8rU6LPYNFgsWuzvb6q9LpX=5duSaKJycUw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2015-03-20 19:26:43 | Re: Remove fsync ON/OFF as a visible option? |
| Previous Message | Stephen Frost | 2015-03-20 19:21:39 | Re: Order of enforcement of CHECK constraints? |