Transient failure of rowsecurity regression test
According to
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dromedary&dt=2014-11-21%2019%3A59%3A50
the order of cascaded drops at one point in the rowsecurity test is not
too stable. This is not terribly surprising since it would depend on
physical row order in pg_depend. I think the easiest fix would be to
adjust the client_min_messages setting so that those messages don't appear
at all.
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
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
According to
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dromedary&dt=2014-11-21%2019%3A59%3A50
the order of cascaded drops at one point in the rowsecurity test is not
too stable. This is not terribly surprising since it would depend on
physical row order in pg_depend. I think the easiest fix would be to
adjust the client_min_messages setting so that those messages don't appear
at all.
Ok, will do.
Thanks!
Stephen
* Stephen Frost (sfrost@snowman.net) wrote:
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
According to
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dromedary&dt=2014-11-21%2019%3A59%3A50
the order of cascaded drops at one point in the rowsecurity test is not
too stable. This is not terribly surprising since it would depend on
physical row order in pg_depend. I think the easiest fix would be to
adjust the client_min_messages setting so that those messages don't appear
at all.Ok, will do.
Done.
Thanks!
Stephen