From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
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-02 00:30:27 |
Message-ID: | 200804020030.m320URl07210@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
> 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.
TODO already has:
* Allow multiple indexes to be created concurrently, ideally via a
single heap scan, and have pg_restore use it
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Smet | 2008-04-02 00:35:17 | Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work |
Previous Message | Stephen Frost | 2008-04-02 00:20:16 | Re: New boxes available for QA |