Insufficient locking for ALTER DEFAULT PRIVILEGES - Mailing list pgsql-hackers

From Vik Fearing
Subject Insufficient locking for ALTER DEFAULT PRIVILEGES
Date
Msg-id 5584A108.7080802@2ndquadrant.fr
Whole thread Raw
Responses Re: Insufficient locking for ALTER DEFAULT PRIVILEGES  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
I came across the following bug this week:

Session 0:
begin;
create schema bug;
alter default privileges in schema bug grant all on tables to postgres;
commit;

Session 1:
begin;
alter default privileges in schema bug grant all on tables to postgres;

Session 2:
alter default privileges in schema bug grant all on tables to postgres;
<hangs>

Session 1:
commit;

Session 2:
ERROR:  tuple concurrently updated
-- 
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: The real reason why TAP testing isn't ready for prime time
Next
From: Jeff Janes
Date:
Subject: Re: pretty bad n_distinct estimate, causing HashAgg OOM on TPC-H