Re: CREATE INDEX and HOT (was Question: pg_classattributes and race conditions ?)

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Subject: Re: CREATE INDEX and HOT (was Question: pg_classattributes and race conditions ?)
Date: 2007-03-17 18:56:58
Message-ID: 1174157818.4160.652.camel@silverbirch.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 2007-03-17 at 23:11 +0530, Pavan Deolasee wrote:

> The algorithm would look like:
>
> 1. Disable HOT-updates

The lock held by CREATE INDEX already prevents HOT updates. So steps 1
and 8 aren't needed.

We need to be clear that we already have a solution to CREATE INDEX
CONCURRENTLY. Do you agree that we do? Does anyone see a problem with
the posted design for that?

Hopefully it is only CREATE INDEX that we need to think about.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2007-03-17 19:14:03 Re: CREATE INDEX and HOT (was Question: pg_classattributes and race conditions ?)
Previous Message Mickael DELOISON 2007-03-17 18:37:25 Project suggestion: benchmark utility for PostgreSQL