Aidan Van Dyk <aidan(at)highrise(dot)ca> writes:
> * Andrew Dunstan <andrew(at)dunslane(dot)net> [080401 08:22]:
>> 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?
> 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)?
Yeah, that should Just Work AFAICS. Note also that this approach would
let you put multiple CPUs to work on the problem, whereas anything
involving stuffing multiple index creations into a single command
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-04-01 14:52:41|
|Subject: Re: Scroll cursor oddity... |
|Previous:||From: Simon Riggs||Date: 2008-04-01 14:46:15|
|Subject: Re: [HACKERS] ANALYZE getting dead tuple counthopelessly wrong|