Andrew Dunstan <and...@dunslane.net> writes:
> The sort of failure shown below has happened a few times recently. See
> recent failures on crake, mastodon and casteroides at
> <http://www.pgbuildfarm.org/cgi-bin/show_failures.pl>. It seems harmless
> enough. Do we need an alternative regression results file, or is there
> some way to prevent this?
There's no real guarantee about the order in which dependency.c lists
the dependencies (it's going to depend on the order in which the rows
happen to be stored in pg_depend). There are some other regression
tests that cope with this by temporarily doing \set VERBOSITY terse
--- if the failures bug you, I'd suggest that, not trying to make an
alternate expected file for every order observed in the field.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
