Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: CREATE INDEX CONCURRENTLY
- From: Simon Riggs <simon(at)2ndquadrant(dot)com>
- To: Dave Page <dpage(at)postgresql(dot)org>
- Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
- Subject: Re: CREATE INDEX CONCURRENTLY
- Date: Fri, 05 Oct 2007 14:05:31 +0100
- Message-id: <1191589531(dot)4223(dot)355(dot)camel(at)ebony(dot)site>
On Fri, 2007-10-05 at 13:55 +0100, Dave Page wrote: > Guillaume Lelarge wrote: > > Simon Riggs a écrit : > >> It would be great if there was a database-level option so that any new > >> indexes would default to using CONCURRENTLY. > >> > >> This would allow production systems to be changed easily using the > >> default of CONCURRENTLY, whereas dev systems won't need that. > >> > >> If not, can we just have a general default of use concurrent builds? > >> > > > > I would be in favor of a database level option. It would be an > > interesting feature for next release. If Dave is OK with this, I will > > add this on our todo page. > > We don't have any infrastructure for saving per-database settings. We > could have a general default easily enough though. Yes, please. Can we turn it on by default? I want to encourage people to use the facilities we've desgined into the database core. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com
- References:
- CREATE INDEX CONCURRENTLY
- From: Simon Riggs
- Re: CREATE INDEX CONCURRENTLY
- From: Guillaume Lelarge
- Re: CREATE INDEX CONCURRENTLY
- From: Dave Page
- CREATE INDEX CONCURRENTLY
- Prev by Date: Re: CREATE INDEX CONCURRENTLY
- Next by Date: SVN Commit by dpage: r6716 - trunk/pgadmin3/pgadmin/dlg
- Previous by thread: Re: CREATE INDEX CONCURRENTLY
- Next by thread: ALTER INDEX set fillfactor
- Indexes: