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

From: "Pavan Deolasee" <pavan(dot)deolasee(at)enterprisedb(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(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 17:51:11
Message-ID: 45FC2A8F.7050005@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
>
> As a result of the issues, I think Pavan is playing safe, to make sure
> there is *an* option, so that we can build upwards from there. The
> proposal is pragmatism only, while we discuss other approaches.
>

Absolutely true. I agree that CHILLing the table with AccessExclusive
lock is not a solution that I like. I was looking at it just as a
stop-gap solution, given the time left for feature freeze.
But if there is something better that we can do, I am for it.

Thanks,
Pavan

--

EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mickael DELOISON 2007-03-17 18:37:25 Project suggestion: benchmark utility for PostgreSQL
Previous Message Tom Lane 2007-03-17 17:51:02 Re: Bug in UTF8-Validation Code?