From: Robert Haas <rhaas@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Add missing binary-upgrade guard.
Date: Thu, 17 Feb 2022 15:58:33 +0000
Message-ID: <E1nKjAv-0006W6-9q@gemulon.postgresql.org> (raw)
Add missing binary-upgrade guard.
Commit 9a974cbcba005256a19991203583a94b4f9a21a9 arranged for
pg_dumpall to preserve tablespace OIDs, but it should only do that
in binary upgrade mode, not all the time.
Reported by Christoph Berg.
Discussion: http://postgr.es/m/YgjwrkEvNEqoz4Vm@msg.df7cb.de
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/138c51b72168e7b57c9edb4e9935274d3abf6bed
Modified Files
--------------
src/bin/pg_dump/pg_dumpall.c | 7 +++++--
1 file changed, 5 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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: rhaas@postgresql.org
Subject: Re: pgsql: Add missing binary-upgrade guard.
In-Reply-To: <E1nKjAv-0006W6-9q@gemulon.postgresql.org>
References: <E1nKjAv-0006W6-9q@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