postgresql/src/bin/pg_upgrade/.gitignore

/pg_upgrade
# Generated by manual invocation
/delete_old_cluster.sh
/delete_old_cluster.bat
/reindex_hash.sql
# Generated by test suite
/log/
/tmp_check/
Convert cvsignore to gitignore, and add .gitignore for build targets. 2010-09-22 12:57:04 +02:00			`/pg_upgrade`
Re-add locally-generated files in pg_upgrade's .gitignore and Makefile This reverts the changes to pg_upgrade's Makefile and .gitignore done in 15b6d21. The TAP tests run in isolation, executing pg_upgrade in tmp_check/ in the build directory so as any files created in the execution path (reindex_hash.sql and delete_old_cluster.{sh,bat}) are never in the tree, so entries are not necessary in this case. However, not having these impacts the cleanliness of the code tree when running ./pg_upgrade directly from src/bin/pg_upgrade/. This commit adds back to .gitignore all the files generated in the execution path, and the Makefile rule to clean them up if they exist. Per gripe from Tom Lane. Discussion: https://postgr.es/m/90595.1655227384@sss.pgh.pa.us 2022-06-15 08:36:16 +02:00			`# Generated by manual invocation`
			`/delete_old_cluster.sh`
			`/delete_old_cluster.bat`
			`/reindex_hash.sql`
Add pg_upgrade test suite It runs the regression tests, runs pg_upgrade on the populated database, and compares the before and after dumps. While not actually a cross-version upgrade, this does detect omissions and bugs in the involved tools from time to time. It's also possible to do a cross-version upgrade by manually supplying parameters. 2011-11-27 21:42:32 +01:00			`# Generated by test suite`
			`/log/`
			`/tmp_check/`