Re: build multiple indexes in single table pass? - Mailing list pgsql-hackers

From Aidan Van Dyk
Subject Re: build multiple indexes in single table pass?
Date
Msg-id 20080401124954.GA6497@yugib.highrise.ca
Whole thread Raw
In response to build multiple indexes in single table pass?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: build multiple indexes in single table pass?  (Andrew Dunstan <andrew@dunslane.net>)
Re: build multiple indexes in single table pass?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
* Andrew Dunstan <andrew@dunslane.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@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

pgsql-hackers by date:

Previous
From: "Pavan Deolasee"
Date:
Subject: Re: build multiple indexes in single table pass?
Next
From: Stuart Brooks
Date:
Subject: Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong