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-14 17:23:04
Message-ID: 90595.1655227384@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:
> Force run of pg_upgrade in the build directory in its TAP test

This commit removed delete_old_cluster.sh etc. from .gitignore,
but they are still generated in the current directory, so after
running a test in a non-VPATH setup I see

$ git status
...
Untracked files:
(use "git add <file>..." to include in what will be committed)
delete_old_cluster.sh

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?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message noreply 2022-06-14 21:10:33 pgsql: Tag refs/tags/REL_14_4 was created
Previous Message Tom Lane 2022-06-13 20:05:02 pgsql: Stamp 14.4.