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

Re: Block B-Tree concept

From: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
To: postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Subject: Re: Block B-Tree concept
Date: 2006-09-27 14:40:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> > I think you build a whole new index named something like ".temp-reindex" and
> > then as the last step of the second transaction delete the old idnex and
> > rename the new index.
> That would require getting exclusive lock on the table.

Just out of curiosity, creating a new index concurrently (or online,
whatever you call it) doesn't require to set an exclusive lock on the
table ? I thought it would, at least swiftly at the end of the
operation, after all it's modifying the table...


In response to


pgsql-hackers by date

Next:From: Albe LaurenzDate: 2006-09-27 14:54:35
Subject: Re: psql service parameter
Previous:From: Tom LaneDate: 2006-09-27 14:34:15
Subject: Re: psql service parameter

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