From: Nathan Bossart <nathan@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix MSVC pg_upgrade test.
Date: Mon, 11 Aug 2025 17:39:36 +0000
Message-ID: <E1ulWUi-0003s7-1T@gemulon.postgresql.org> (raw)
Fix MSVC pg_upgrade test.
In the back-branch versions of commit 71ea0d6795, I missed updating
this test to use --restrict-key so that the generated dump output
is comparable.
Per buildfarm member hamerkop.
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Security: CVE-2025-8714
Backpatch-through: 13-14
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/8967c33c67b85a33fee5ffb9bf16a67b640bacb8
Modified Files
--------------
src/tools/msvc/vcregress.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: nathan@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix MSVC pg_upgrade test.
In-Reply-To: <E1ulWUi-0003s7-1T@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox