-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Jul 10, 2007 at 10:41:31AM -0400, Tom Lane wrote: > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > The following command sequence appears to lock up the database system: > > BEGIN; > > LOCK pg_authid; > > PREPARE TRANSACTION 'foo'; > > \q > > > After that you can't connect anymore, even in single-user mode. The > > only way I could find is to clear out the pg_twophase directory, but > > I'm not sure whether it is safe to do that. > > > Should this be prevented somehow, and is there a better recovery path? > > AFAICS this is just one of many ways in which a superuser can shoot > himself in the foot; I'm not eager to try to prevent it. > > Right offhand, clearing pg_twophase while the system is stopped should > be safe enough.
It might make sense then to clear the pg_twophase directory on DB startup. Nobody would expect the locks to persist a database restart -- or am I way off? Regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGlFdxBcgs9XrR2kYRAp9/AJ4s8fBkhtaxqfu0QxBhSN2lCi++zgCfRsS9 Jpjv6513ubPtfldf2fItzj0= =KAW0 -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings