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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Force run of pg_upgrade in the build directory in its TAP test
Дата
Msg-id 90595.1655227384@sss.pgh.pa.us
обсуждение исходный текст
Ответ на pgsql: Force run of pg_upgrade in the build directory in its TAP test  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: pgsql: Force run of pg_upgrade in the build directory in its TAP test  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-committers
Michael Paquier <michael@paquier.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



В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Stamp 14.4.
Следующее
От: noreply@postgresql.org
Дата:
Сообщение: pgsql: Tag refs/tags/REL_14_4 was created