Insufficient locking for ALTER DEFAULT PRIVILEGES

From: Vik Fearing <vik(at)2ndquadrant(dot)fr>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Insufficient locking for ALTER DEFAULT PRIVILEGES
Date: 2015-06-19 23:08:56
Message-ID: 5584A108.7080802@2ndquadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

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