Re: Potential GIN vacuum bug

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Heikki <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Potential GIN vacuum bug
Date: 2015-08-17 22:02:21
Message-ID: 20150817220221.GE5232@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Janes wrote:

> The attached patch takes a ShareUpdateExclusiveLock lock on the index in
> order to clean the pending list.

Does it take a lock on the table also? Because if not ...

> One potential problem is how it will interact with "create index
> concurrently".

... then I don't understand how you could have a problem here. Surely
no pending list cleanup can happen concurrently with the index being
created?

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rahila Syed 2015-08-17 22:07:54 Re: [PROPOSAL] VACUUM Progress Checker.
Previous Message Tom Lane 2015-08-17 21:46:35 Re: Error message with plpgsql CONTINUE