| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Chris Browne <cbbrowne(at)acm(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 2PC-induced lockup |
| Date: | 2007-07-11 15:44:12 |
| Message-ID: | 4694FACC.4030800@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Chris Browne wrote:
> If one locks certain vital system resources, as part of that PREPAREd
> transaction, that evidently causes some problems, alas...
>
> The right resolution to this is not, a priori, evident yet.
It's not? I agree with Tom here; this is just one of the numerous things
you can do to screw up your database as a superuser. Why would you LOCK
the pg_auth table, or any other system table for that matter, in the
first place? Let alone in a distributed transaction.
FWIW, deleting the files from pg_twophase is safe when the system is
shut down.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-07-11 15:54:50 | Re: PQescapeBytea* version for parameters |
| Previous Message | Stefan Kaltenbrunner | 2007-07-11 15:42:00 | minor compiler warning on OpenBSD |