Re: pgsql: Force run of pg_upgrade in the build directory in its TAP test

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Force run of pg_upgrade in the build directory in its TAP test
Date: 2022-06-15 00:11:59
Message-ID: 191585.1655251919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Tue, Jun 14, 2022 at 01:23:04PM -0400, Tom Lane wrote:
>> I suppose it would be too user-unfriendly to generate those scripts
>> underneath $PGDATA, so don't we need to put back the .gitignore
>> entries?

> delete_old_cluster.sh is generated within tmp_check/ in a non-VPATH
> build:

Sorry, I wasn't very clear: I'd tested pg_upgrade with a manual
invocation, like "./pg_upgrade -d ...". That used to be OK and
now it leaves junk around. I think it's worth keeping the
.gitignore entries (and I guess the "make clean" rule step too)
so that that approach still works without making a mess.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2022-06-15 00:48:14 Re: pgsql: Force run of pg_upgrade in the build directory in its TAP test
Previous Message Michael Paquier 2022-06-15 00:00:00 Re: pgsql: Force run of pg_upgrade in the build directory in its TAP test