RE: pg_upgrade: Pass -j down to vacuumdb

From: "Jamison, Kirk" <k(dot)jamison(at)jp(dot)fujitsu(dot)com>
To: "'jesper(dot)pedersen(at)redhat(dot)com'" <jesper(dot)pedersen(at)redhat(dot)com>, "Michael Paquier" <michael(at)paquier(dot)xyz>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "fabriziomello(at)gmail(dot)com" <fabriziomello(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "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-31 00:59:46
Message-ID: D09B13F772D2274BB348A310EE3027C6416377@g01jpexmbkw24
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

On January 29, 2019 8:19 PM +0000, Jesper Pedersen wrote:
>On 1/29/19 12:08 AM, Michael Paquier wrote:
>> I would document the optional VACUUM_OPTS on the page of pg_upgrade.
>> If Peter thinks it is fine to not do so, that's fine for me as well.
>I added most of the documentation back, as requested by Kirk.

Actually, I find it useful to be documented. However, major contributors have higher opinions in terms of experience, so I think it's alright with me not to include the doc part if they finally say so.

>> It seems to me that the latest patch sent is incorrect for multiple
>> reasons:
>> 1) You still enforce -j to use the number of jobs that the caller of
>> pg_upgrade provides, and we agreed that both things are separate
>> concepts upthread, no? What has been suggested by Alvaro is to add a
>> comment so as one can use VACUUM_OPTS with -j optionally, instead of
>> suggesting a full-fledged vacuumdb command which depends on what
>> pg_upgrade uses. So there is no actual need for the if/else
>> complication business.

> I think it is ok for the echo command to highlight to the user that running --analyze-only using the same amount of jobs will give a faster result.

I missed that part.
IIUC, using the $VACUUMDB_OPTS variable would simplify and correct the usage of jobs for vacuumdb. (pg_upgrade jobs is not equal to vacuumdb jobs) Plus, it might simplify and reduce the number of additional lines.
Tom Lane also suggested above to make the script absorb the value from env.
Would that address your concern of getting a faster result, yes?

Kirk Jamison

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-01-31 01:18:31 Re: [PATCH] Pass COPT and PROFILE to CXXFLAGS as well
Previous Message Michael Paquier 2019-01-31 00:44:51 Re: [PATCH] Pass COPT and PROFILE to CXXFLAGS as well