| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: more than one index in a single heap pass? |
| Date: | 2009-07-14 23:04:59 |
| Message-ID: | 407d949e0907141604m30309312ua7e805a085c5d84c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 14, 2009 at 8:50 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-07-14 23:11:41 | Re: navigation menu for documents |
| Previous Message | Richard Huxton | 2009-07-14 22:57:07 | Re: navigation menu for documents |