| From: | Laurent Laborde <kerdezixe(at)gmail(dot)com> |
|---|---|
| To: | Cédric Villemain <cedric(dot)villemain(at)dalibo(dot)com> |
| Cc: | jd(at)commandprompt(dot)com, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-16 16:01:56 |
| Message-ID: | 8a1bfe660902160801x4a544cb7rd6ea273c7c3fa567@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 16, 2009 at 12:10 PM, Cédric Villemain
<cedric(dot)villemain(at)dalibo(dot)com> wrote:
>>
>> is -j already affected ?
>
> else (like make):
>
> -j [jobs], --jobs[=jobs]
> Specifies the number of jobs (pg_restore) to run simultaneously. If the -j
> option is given without an argument, pg_restore will not limit the number of
> jobs that can run simultaneously.
I like both -j and -w.
-j because we all know "make -j"
-w because i like --num-workers
--
F4FQM
Kerunix Flan
Laurent Laborde
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-02-16 16:14:27 | Re: SE-PostgreSQL and row level security |
| Previous Message | Tom Lane | 2009-02-16 15:59:38 | Re: SE-PostgreSQL and row level security |