Re: parallel pg_restore - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: parallel pg_restore
Date
Msg-id 1222106611.4445.210.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: parallel pg_restore  (Joshua Drake <jd@commandprompt.com>)
Responses Re: parallel pg_restore  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Mon, 2008-09-22 at 09:30 -0700, Joshua Drake wrote:
> On Mon, 22 Sep 2008 17:24:28 +0100
> Simon Riggs <simon@2ndQuadrant.com> wrote:
> 
> > > More importantly, I'm not convinced it's a good idea. It seems more
> > > like a footgun that will potentially try to launch thousands of
> > > simultaneous restore connections. I should have thought that
> > > optimal performance would be reached at some small multiple (say
> > > maybe 2?) of the number of CPUs on the server. You could achieve
> > > unlimited parallelism by saying something like --jobs=99999, but
> > > I'd rather that were done very explicitly instead of as the default
> > > value of the parameter.
> > 
> > OK, sounds best.
> > 
> 
> I will not argue vehemently here but I will say that "jobs" doesn't
> seem correct. The term "workers" seems more appropriate.

Agreed, but most utilities have "j" free but not w, p, t or other
letters that might be synonyms.

j is at least used for exactly this purpose in other tools.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: "Jaime Casanova"
Date:
Subject: Re: [PATCH] allow has_table_privilege(..., 'usage') on sequences
Next
From: Simon Riggs
Date:
Subject: Re: Initial prefetch performance testing