Re: Test 002_pg_upgrade fails with olddump on Windows
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Alexander Lakhin <exclusion@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-12-05T07:56:04Z
Lists: pgsql-hackers
On Sat, Nov 25, 2023 at 11:00:01PM +0300, Alexander Lakhin wrote:
> diff --git a/src/bin/pg_upgrade/t/002_pg_upgrade.pl b/src/bin/pg_upgrade/t/002_pg_upgrade.pl
> index c6d83d3c21..d34b45e346 100644
> --- a/src/bin/pg_upgrade/t/002_pg_upgrade.pl
> +++ b/src/bin/pg_upgrade/t/002_pg_upgrade.pl
> @@ -293,6 +293,7 @@ if (defined($ENV{oldinstall}))
> }
>
> open my $fh, ">", $dump1_file or die "could not open dump file";
> + binmode $fh;
> print $fh $dump_data;
> close $fh;
There is something I don't get here. The old and new dump files
should be processed in filter_dump(), where
AdjustUpgrade::adjust_old_dumpfile does the following so binmode
should not be needed:
# use Unix newlines
$dump =~ s/\r\n/\n/g;
Or you have used the test suite with an old installation that has the
same major version as the new installation, meaning that the filtering
was not happening, still you have detected some diffs? It sounds to
me that we should just apply the filters to the dumps all the time if
you have used matching versions. The filtering would remove only the
comments, some extra newlines and replace the CRLFs in this case.
--
Michael
Commits
-
Fix path of regress shared library in pg_upgrade test
- 24482838c2c4 15.6 landed
- a09aa18eaa6a 16.2 landed
- e5b8c4f68fa5 17.0 landed
-
Apply filters to dump files all the time in 002_pg_upgrade.pl
- f0b53daa2c76 15.6 landed
- a499c08dca5e 16.2 landed
- bfc677c3bc31 17.0 landed