| From: | Joshua Drake <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: parallel pg_restore |
| Date: | 2008-09-23 19:43:51 |
| Message-ID: | 20080923124351.4c2ba1f0@jd-laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 23 Sep 2008 08:44:19 +0100
Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
>
> On Mon, 2008-09-22 at 15:05 -0400, Andrew Dunstan wrote:
>
> > j and m happen to be two of those that are available.
> >
> > I honestly don't have a terribly strong opinion about what it
> > should be called. I can live with jobs or multi-threads.
>
> Perhaps we can use -j for jobs and -m for memory, so we can set memory
> available across all threads with a single total value.
>
> I can live with jobs or multi-threads also, whichever we decide.
> Neither one is confusing to explain.
>
Memory? Where did that come from. Andrew is that in your spec?
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-09-23 19:53:59 | Re: parallel pg_restore |
| Previous Message | Joshua Drake | 2008-09-23 19:43:20 | Re: parallel pg_restore |