| 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 21:11:52 |
| Message-ID: | 1174165912.4160.660.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2007-03-18 at 00:44 +0530, Pavan Deolasee wrote:
> Simon Riggs wrote:
> >
> > 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?
If we have solved CREATE INDEX CONCURRENTLY, then I would propose that
this becomes the default option for creating an index, when the
statement is issued outside of a statement block.
That seems better than reminding everybody to run with the CONCURRENTLY
option, or advise them of different performance characteristics or
behaviour of the normal CREATE INDEX route.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grzegorz Jaskiewicz | 2007-03-17 21:14:35 | Re: [PATCHES] Bitmapscan changes |
| Previous Message | Florian G. Pflug | 2007-03-17 20:44:29 | Re: Project suggestion: benchmark utility for PostgreSQL |