Re: pg_restore --multi-thread

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_restore --multi-thread
Date: 2009-02-12 16:50:26
Message-ID: 1234457426.9467.33.camel@jd-laptop.pragmaticzealot.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2009-02-12 at 11:47 -0500, Andrew Dunstan wrote:
>
> Joshua D. Drake wrote:
> > On Thu, 2009-02-12 at 11:32 -0500, Tom Lane wrote:
> >
> >> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> >>
> >>> The implementation is actually different across platforms: on Windows
> >>> the workers are genuine threads, while elsewhere they are forked
> >>> children in the same fashion as the backend (non-EXEC_BACKEND case). In
> >>> either case, the program will use up to NUM concurrent connections to
> >>> the server.
> >>>
> >> How about calling it --num-connections or something like that? I agree
> >> with Peter that "thread" is not the best terminology on platforms where
> >> there is no threading involved.
> >>
> >
> > --num-workers or --num-connections would both work.
> >
> >
>
> *shrug* whatever. What should the short option be (if any?). -n is
> taken, so -N ?

Works for me.

>
> cheers
>
> andrew
>
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-02-12 17:01:27 Re: pg_migrator and handling dropped columns
Previous Message Dickson S. Guedes 2009-02-12 16:49:54 64 bit PostgreSQL 8.3.6 build on AIX 5300 with GCC 4.2.0 - fail on pg_regress