From: | Cédric Villemain <cedric(dot)villemain(at)dalibo(dot)com> |
---|---|
To: | jd(at)commandprompt(dot)com |
Cc: | 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 11:10:01 |
Message-ID: | 49994989.4010602@dalibo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Cédric Villemain a écrit :
> Joshua D. Drake a écrit :
>> 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.
>
> 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.
>
>
>>> cheers
>>>
>>> andrew
>>>
>
>
- --
Cédric Villemain
Administrateur de Base de Données
Cel: +33 (0)6 74 15 56 53
http://dalibo.com - http://dalibo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkmZSYkACgkQo/dppWjpEvwO8wCfUFztxS7cmRX+hhbVphfqqDzo
ZzUAniFwmwhI9y6f9Mndg9CPGlQiOaae
=fDYZ
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2009-02-16 11:33:40 | Re: Which installation parts are backward compatible? |
Previous Message | Gregory Stark | 2009-02-16 10:54:32 | Re: SE-PostgreSQL and row level security |