From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
Subject: | Re: Concurrent connections in psql |
Date: | 2007-03-27 21:13:47 |
Message-ID: | 1175030027.4386.226.camel@silverbirch.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2007-03-27 at 17:11 -0400, Andrew Dunstan wrote:
> Simon Riggs wrote:
> >
> > I would love, love, love to be able to use this syntax within pg_dump as
> > well, so we can create multiple indexes in parallel at restore time.
> > Anyone fancy adding that as well? We should be able to speed up overall
> > index builds by x2 using concurrent builds.
> You will need to teach pg_restore any trick you use here - it doesn't
> use psql.
The proposed change is to psql and making it work with pg_restore would
take a lot more thought, so probably not an 8.3 item. Should we make it
to neither because we can't make it to both?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-03-27 21:24:17 | Re: Concurrent connections in psql |
Previous Message | Andrew Dunstan | 2007-03-27 21:11:01 | Re: Concurrent connections in psql |