Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Add DROP INDEX CONCURRENTLY [IF EXISTS], uses ShareUpdateExclusi

From: Shigeru HANADA <shigeru(dot)hanada(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add DROP INDEX CONCURRENTLY [IF EXISTS], uses ShareUpdateExclusi
Date: 2012-04-06 11:29:14
Message-ID: 4F7ED38A.5050309@gmail.com (view raw or flat)
Thread:
Lists: pgsql-committers
(2012/04/06 18:27), Simon Riggs wrote:
> Add DROP INDEX CONCURRENTLY [IF EXISTS], uses ShareUpdateExclusiveLock
> src/backend/catalog/index.c                |  139 ++++++++++++++++++++++++++-

I got a compiler warning "set but not used" about newly added variable
indexlocktag.  Is it ok?

Regards,
-- 
Shigeru HANADA

In response to

pgsql-committers by date

Next:From: Tom LaneDate: 2012-04-06 19:02:50
Subject: pgsql: Allow statistics to be collected for foreign tables.
Previous:From: Simon RiggsDate: 2012-04-06 09:27:22
Subject: pgsql: Add DROP INDEX CONCURRENTLY [IF EXISTS],uses ShareUpdateExclusi

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group