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

Re: build multiple indexes in single table pass?

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: build multiple indexes in single table pass?
Date: 2008-04-01 12:49:54
Message-ID: 20080401124954.GA6497@yugib.highrise.ca (view raw or flat)
Thread:
Lists: pgsql-hackers
* Andrew Dunstan <andrew(at)dunslane(dot)net> [080401 08:22]:
> 
> From the "idle thoughts in the middle of the night" department:
> 
> I don't know if this has come up before exactly, but is it possible that 
> we could get a performance gain from building multiple indexes from a 
> single sequential pass over the base table? If so, that would probably 
> give us  a potential performance improvement in pg_restore quite apart 
> from the projected improvement to be got from running several steps in 
> parallel processes. The grammar might look a bit ugly, but I'm sure we 
> could finesse that.

I've not looked at any of the code, but would the "synchronized scans"
heap machinery help the multiple index creations walk the heap together,
basically giving you this for free (as long as you start concurrent
index creation)?

a.

-- 
Aidan Van Dyk                                             Create like a god,
aidan(at)highrise(dot)ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

In response to

Responses

pgsql-hackers by date

Next:From: Stuart BrooksDate: 2008-04-01 13:00:31
Subject: Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong
Previous:From: Pavan DeolaseeDate: 2008-04-01 12:47:31
Subject: Re: build multiple indexes in single table pass?

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