Re: pg_upgrade: Pass -j down to vacuumdb

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: jesper(dot)pedersen(at)redhat(dot)com, fabriziomello(at)gmail(dot)com
Cc: "Jamison, Kirk" <k(dot)jamison(at)jp(dot)fujitsu(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: pg_upgrade: Pass -j down to vacuumdb
Date: 2019-01-28 20:50:20
Message-ID: e103a8a1-a6f1-5709-6ac6-95684fd5bff2@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 28/01/2019 17:47, Jesper Pedersen wrote:
> On 1/28/19 11:30 AM, Fabrízio de Royes Mello wrote:
>> IMHO you should use long option name '--jobs' like others.
>>
>
> Thanks for your feedback !
>
> Done, and v4 attached.

I would drop the changes in pgupgrade.sgml. We don't need to explain
what doesn't happen, when nobody before now ever thought that it would
happen.

Also, we don't need the versioning stuff. The new cluster in pg_upgrade
is always of the current version, and we know what that one supports.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-01-28 20:50:22 Re: Proposed refactoring of planner header files
Previous Message Nishant, Fnu 2019-01-28 20:47:04 Re: possible deadlock: different lock ordering for heap pages