From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Ian Lawrence Barwick <barwick@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour
Date: Fri, 23 Oct 2020 09:56:03 -0400
Message-ID: <145522.1603461363@sss.pgh.pa.us> (raw)
In-Reply-To: <20201023134611.GG16415@tamriel.snowman.net>
References: <CAB8KJ=jYHgnxLLZSNJz7gBTck4TxomngCmGkw3nEMSNF0yL6wA@mail.gmail.com>
<CAB8KJ=h-XALik4M7gv-pX48=+SPWexfaYwa+yTnPwD3DxceXrg@mail.gmail.com>
<e4934710-73cb-6eef-fd35-6fcfd05f381b@iki.fi>
<20201023134611.GG16415@tamriel.snowman.net>
Stephen Frost <sfrost@snowman.net> writes:
> Isn't this a bit pre-mature as we still support running pg_dump against
> 8.0 clusters..?
The removed para was discussing the behavior of pg_dump itself. What
server version you run it against isn't relevant.
Having said that, there are a *lot* of past-their-sell-by-date bits
of info throughout our documentation, because we don't have any sort
of policy or mechanism for getting rid of this kind of backwards
compatibility note. Maybe we should first try to agree on a policy
for when it's okay to remove such info.
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, sfrost@snowman.net, hlinnaka@iki.fi, barwick@gmail.com
Subject: Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour
In-Reply-To: <145522.1603461363@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