is it good to allow locks on system tables at all?
i am not so sure. have seen some disaster in the past with that. just
consider somebody placing ACCESS EXCLUSIVE LOCK on a system table. it
is basically denial of service.
best regards,
hans
On Jul 10, 2007, at 3:14 PM, Peter Eisentraut wrote:
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?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---------------------------(end of
broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
--
Cybertec Geschwinde & Schönig GmbH
Gröhrmühlgasse 26, 2700 Wiener Neustadt
Tel: +43/1/205 10 35 / 340
www.postgresql.at, www.cybertec.at
