Re: pg_restore --multi-thread - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: pg_restore --multi-thread
Date
Msg-id 1234456658.9467.27.camel@jd-laptop.pragmaticzealot.org
Whole thread Raw
In response to Re: pg_restore --multi-thread  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_restore --multi-thread
Re: pg_restore --multi-thread
List pgsql-hackers
On Thu, 2009-02-12 at 11:32 -0500, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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.

Joshua D. Drake

> 
>             regards, tom lane
> 
-- 
PostgreSQL - XMPP: jdrake@jabber.postgresql.org  Consulting, Development, Support, Training  503-667-4564 -
http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
 



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_restore --multi-thread
Next
From: Bruce Momjian
Date:
Subject: Re: some questions about SELECT FOR UPDATE/SHARE