Re: pg_upgrade analyze script - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_upgrade analyze script
Date
Msg-id ea403f46-2b33-a7de-618e-9cab35a698c8@enterprisedb.com
Whole thread Raw
In response to Re: pg_upgrade analyze script  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pg_upgrade analyze script  (Michael Paquier <michael@paquier.xyz>)
Re: pg_upgrade analyze script  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On 2020-11-09 11:22, Magnus Hagander wrote:
>> I have spotted one small-ish thing.  This patch is missing to update
>> the following code in vcregress.pl:
>>      print "\nSetting up stats on new cluster\n\n";
>>      system(".\\analyze_new_cluster.bat") == 0 or exit 1;
> Ah, nice catch -- thanks! I guess this is unfortunately not a test
> that's part of what cfbot tests.
> 
> Untested on Windows, but following the patterns of the rows before it.
> I will go ahead and push this version in a bit.

You should just remove those calls.  There is no need to replace them 
with vacuumdb calls.  The reason those calls were there is that they 
were testing the generated script itself.  If the script is gone, there 
is no more need.  There are already separate tests for testing vacuumdb.




pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Rethinking LOCK TABLE's behavior on views
Next
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: vacuum -vs reltuples on insert only index