Greg Stark wrote:
On Tue, Jul 14, 2009 at 8:50 PM, Tom Lane<t...@sss.pgh.pa.us> wrote:
Alvaro Herrera <alvhe...@commandprompt.com> writes:
Andrew Dunstan wrote:
I was just wondering idly today if we could usefully build a number of
indexes at the same time in a single pass over the heap, or could it be
that we wouldn't gain much? I haven't even got around to thinking about
any syntax for it.
Could we make it work on two backends building one index each in
synchronized scans?
Don't we more or less have that already?
Wasn't that a big part of the point of the "parallel pg_restore" feature?
Well, yes, it's some of it, and in theory Tom's late addition of a queue
that gets all the dependencies of a table as soon as the table data is
restored should make that work better. But of course, that's not the
only time indexes are created, and each index creation command will be
doing its own heap processing, albeit that synchronised scanning will
make that lots cheaper.
As I said originally, it was just an idle thought that came to me today.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
