Andrew Sullivan <[EMAIL PROTECTED]> writes:
> But the other problem I see here is that the solution hits more than
> just the problematic state. If we have bad pages on disk, for
> instance, we zero pages; we don't drop the table. Similarly, it
> seems that all that's necessary here is an external tool to grovel
> through the prepared transaction files and somehow figure out what
> locks, if any, they entail.
Something equivalent to pg_filedump or xlogdump for 2PC state files
would be worth having for development/debugging purposes, quite aside
from any possible usefulness for getting out of this type of
predicament. Any volunteers out there to write/maintain such a utility?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
