From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vera Gangeskar Johne <vjohne@salesforce.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: pg_dump is not backwards compatible in PG12
Date: Wed, 12 Feb 2020 14:49:27 -0500
Message-ID: <10870.1581536967@sss.pgh.pa.us> (raw)
In-Reply-To: <CAPAx+ExTJukgwJME7q+p=brk8mxLZ=RJT29TkqYpoFz+1UpKkA@mail.gmail.com>
References: <CAPAx+ExTJukgwJME7q+p=brk8mxLZ=RJT29TkqYpoFz+1UpKkA@mail.gmail.com>
Vera Gangeskar Johne <vjohne@salesforce.com> writes:
> PG 12 bumped the pg_backup_archiver version to 1.14, however this version
> is not supported in past versions of pg_backup_archiver, resulting in
> restores to earlier versions not working.
Yup. Use a newer version of pg_restore.
> 1. Is it expected that pg_dump will produce backwards incompatible dumps?
It's happened before, and it will happen again, no doubt.
> 2. The release notes don't mention this at all as far as I could see.
> Should they?
Possibly. In practice, backwards-incompatibility of the SQL contained
in the dump is a bigger issue most of the time than the dump file format
proper, and there are issues of that sort in almost every major release.
> 3. Should this be a bug?
No. It's impractical to freeze that file format, because we keep adding
new things that pg_dump has to deal with (as the version history you found
shows). Maybe it could've been designed to be more extension-friendly,
but such a redesign would itself be backwards-incompatible.
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, vjohne@salesforce.com
Subject: Re: pg_dump is not backwards compatible in PG12
In-Reply-To: <10870.1581536967@sss.pgh.pa.us>
References: <CAPAx+ExTJukgwJME7q+p=brk8mxLZ=RJT29TkqYpoFz+1UpKkA@mail.gmail.com> <10870.1581536967@sss.pgh.pa.us>
* 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