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
