| From: | Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Dilip kumar <dilip(dot)kumar(at)huawei(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Euler Taveira <euler(at)timbira(dot)com(dot)br> |
| Subject: | Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ] |
| Date: | 2014-07-02 18:31:09 |
| Message-ID: | CAD21AoDRLnYFx8kbeNdUjWuJJDwhpJGFmN6Qy2=wKMNuEDD1+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 2, 2014 at 2:27 PM, Dilip kumar <dilip(dot)kumar(at)huawei(dot)com> wrote:
> On 01 July 2014 22:17, Sawada Masahiko Wrote,
>
>
>> I have executed latest patch.
>> One question is that how to use --jobs option is correct?
>> $ vacuumdb -d postgres --jobs=30
>>
>> I got following error.
>> vacuumdb: unrecognized option '--jobs=30'
>> Try "vacuumdb --help" for more information.
>>
>
> Thanks for comments, Your usage are correct, but there are some problem in code and I have fixed the same in attached patch.
>
This patch allows to set 0 to -j option?
When I set 0 to -j option, I think that the behavior of this is same
as when I set to 1.
Regards,
-------
Sawada Masahiko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2014-07-02 18:45:29 | log_error_verbosity and unexpected errors |
| Previous Message | Alvaro Herrera | 2014-07-02 18:15:19 | Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ] |