W dniu 2012-02-27 23:57, Tom Lane pisze:
Hm. We've seen occasional reports of this sort of behavior (that is,
DROP of a schema failing to cascade to all the contained objects) but
never been able to reproduce it. If you do see it happen again, and
can work out a scenario that causes it (even only intermittently)
we'd love to have a test case.
I think we could try to play here a bit and arrange some possible scenarios with (abnormal)
execution of the the script which creates/drops the schemas and see what happens.
Could you help me find what is the particular order of cascaded table drops? Is it the exact same
order as indicated in the list following the NOTICE: drop cascades to xx other objects? I can see
that logged order is the same as the order of table creation - so order by oid? If yes then the
orphaned two tables of my case are the very last ones expected to be dropped.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
