Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kVxOf-0007nu-7D for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Oct 2020 13:46:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kVxOd-0005c4-KU for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Oct 2020 13:46:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kVxOd-0005bx-D9 for pgsql-hackers@lists.postgresql.org; Fri, 23 Oct 2020 13:46:19 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kVxOX-0006Fj-5H for pgsql-hackers@postgresql.org; Fri, 23 Oct 2020 13:46:18 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 81DF85F799; Fri, 23 Oct 2020 09:46:11 -0400 (EDT) Date: Fri, 23 Oct 2020 09:46:11 -0400 From: Stephen Frost To: Heikki Linnakangas Cc: Ian Lawrence Barwick , pgsql-hackers Subject: Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour Message-ID: <20201023134611.GG16415@tamriel.snowman.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="rCwQ2Y43eQY6RBgR" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --rCwQ2Y43eQY6RBgR Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Heikki Linnakangas (hlinnaka@iki.fi) wrote: > On 06/10/2020 15:15, Ian Lawrence Barwick wrote: > >2020=E5=B9=B410=E6=9C=886=E6=97=A5(=E7=81=AB) 21:13 Ian Lawrence Barwick= : > >>The pg_dump doc page [1], under the -t/--table option, contains a Note > >>documenting the behavioural differences introduced in PostgreSQL 8.2. > >> > >>As it's been almost exactly 14 years since that note was added [2], I s= uggest > >>it can be removed entirely. > >> > >>[1] https://www.postgresql.org/docs/current/app-pgdump.html > >>[2] https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dblobdiff;= f=3Ddoc/src/sgml/ref/pg_dump.sgml;h=3D9aa4baf84e74817a3c3e8359b2c4c8a847fda= 987;hp=3Ddeafd7c9a989c2cbce3979d94416a298609f5e84;hb=3D24e97528631e7e810ce6= 1fc0f5fbcaca0c001c4c;hpb=3D77d2b1b625c7decd7a25ec865bced3b927de6d4b > > > > > >Oh yes, I was planning to attach an ultra-trivial patch for that too. >=20 > Applied, thanks. Isn't this a bit pre-mature as we still support running pg_dump against 8.0 clusters..? Removing support for older clusters is certainly something we can discuss but I don't know that it makes sense to just piecemeal pull things out. I get that this was just a documentation note, but, still, we do support pg_dump run against 8.0 and 8.1 clusters, at least today. Thanks, Stephen --rCwQ2Y43eQY6RBgR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJfkt6jAAoJEO1sijiDR2RVl18QAJ+KbYYM9KU7bfr7hwPo+iIY GtzQzGmOWczw4IyU3VrCyVLWS/cRSImoQogIN5EsdmAYM9TeZgaP9+8MbKndx61G LhELqFLXo70RuUmasKlx4pcLrbPDYqo6n8mNLdKb7kydrSRSLeIzqJJFSm7EdyUO 8FQ8f4P4EUbW0V7cpKqa3XHpy2ZeFqQYGeyf38jSNzSFpTESkjq8k8tLIQLFFEps ckghQmhj8VqJ9y9BpyWYd2VtHFBpiIItvGzzkeQrf1Kx2xj6K6224A02Sl8r+i39 92g6svzVqq3DRNKQ+/5hlMAl9hUReQn4Nq8PE65P65BSqIiKVLE8QPIcybTW7UJX hdiyI/v8uSFqNKV3D1ByC/ut0Mr8O/zF52R5aWEG2SkF2vU+7eT413b9hc3h4r0W irlT1JCgLGkq3jDonKdbhcPeusO4v87aBIvuKFbpw+8DJ2JD0czD+obDJ/nFTYaA b1zlUsC8//f1lRNSNoyWWqJqYMbIniyPT7OfgwyRQNd34dOVb5IkatVzhBMCCWqw KZ08vuSHW8mk/6q+XLtL6nIGilIhsz3gfUIVWHkQcEtMgFj2B+EjJhK9CaiMXCAK Z2tbnqc+9k7ULwVYXgPyZjy1yuEYNV9z/YXgJX55n9tXqmm9JOtiHIGdmWwb0SV+ xAbue0Z56GlAGQ00Rz2+ =Bmbi -----END PGP SIGNATURE----- --rCwQ2Y43eQY6RBgR--