On Fri, Mar 20, 2015 at 4:37 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > =?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= <fabriziome...@gmail.com> writes: > > On Fri, Mar 20, 2015 at 4:19 PM, Peter Geoghegan <p...@heroku.com> wrote: > >> On Fri, Mar 20, 2015 at 12:15 PM, Tom Lane <t...@sss.pgh.pa.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()). >
Isn't better do this to read pg_constraint in name order? - conscan = systable_beginscan(conrel, ConstraintRelidIndexId, true, + conscan = systable_beginscan(conrel, ConstraintNameNspIndexId, true, 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
