Re: 2PC-induced lockup

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Chris Browne <cbbrowne(at)acm(dot)org>
Subject: Re: 2PC-induced lockup
Date: 2007-07-11 19:12:11
Message-ID: 46952B8B.1090401@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
> Heikki Linnakangas wrote:
>> 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.
>
> Well, my test case arose from a real application scenario, not an
> attempt to destroy my database system.

Why does the application LOCK pg_auth?

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-07-11 19:53:42 Re: 2PC-induced lockup
Previous Message Peter Eisentraut 2007-07-11 19:06:45 Re: 2PC-induced lockup