Re: pg_upgrade analyze script

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Georgios Kokolatos <gkokolatos(at)protonmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_upgrade analyze script
Date: 2020-11-11 15:51:27
Message-ID: CABUevEyvmJ+FA6g-crCHBEY02kfN0Zyj2J3ZZSZEGwTRYUEr4w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 11, 2020 at 2:21 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Tue, Nov 10, 2020 at 10:21:04AM +0900, Michael Paquier wrote:
> > On Mon, Nov 09, 2020 at 03:47:22PM +0100, Peter Eisentraut wrote:
> >> 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.
> >
> > True, 102_vacuumdb_stages.pl already does all that.
>
> Let's fix that. From what I can see it only involves the attached,
> and as a bobus it also reduces the number of extra characters showing
> on my terminal after running pg_upgrade tests.

Gah. For some reason, I did not spot this email until after I had
applied the other patch. And not only that, I also missed one line in
my patch that you included in yours :/

My apologies.

--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2020-11-11 15:53:05 Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Previous Message Magnus Hagander 2020-11-11 15:50:24 Re: pg_upgrade analyze script