Re: 2PC-induced lockup
| От | Heikki Linnakangas |
|---|---|
| Тема | Re: 2PC-induced lockup |
| Дата | |
| Msg-id | 4694FACC.4030800@enterprisedb.com обсуждение исходный текст |
| Ответ на | Re: 2PC-induced lockup (Chris Browne <cbbrowne@acm.org>) |
| Ответы |
Re: 2PC-induced lockup
Re: 2PC-induced lockup |
| Список | 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
В списке pgsql-hackers по дате отправления: