| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Greg Stark <gsstark(at)mit(dot)edu>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: more than one index in a single heap pass? |
| Date: | 2009-07-15 14:53:24 |
| Message-ID: | 22494.1247669604@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Well, TODO has:
> Allow multiple indexes to be created concurrently, ideally via a
> single heap scan, and have pg_restore use it
> Isn't this already largely done by parallel pg_restore work?
> so we have to decide if we still want that item. I think what we don't
> have is a way to create multiple indexes simultaneously via SQL.
And if we did build that, people would be bleating because it could only
make use of one CPU. I think multiple backends using the existing
syncscan infrastructure meets this need pretty well already.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Blewett | 2009-07-15 15:51:46 | Add encoding support to COPY |
| Previous Message | Bruce Momjian | 2009-07-15 14:45:56 | Re: more than one index in a single heap pass? |