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 1kVyPQ-00024S-1E for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Oct 2020 14:51:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kVyPN-0005Cy-Ul for pgsql-hackers@arkaria.postgresql.org; Fri, 23 Oct 2020 14:51:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kVyPN-0005Cr-NV for pgsql-hackers@lists.postgresql.org; Fri, 23 Oct 2020 14:51:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kVyPL-00070f-LT for pgsql-hackers@postgresql.org; Fri, 23 Oct 2020 14:51:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09NEp3cI147813; Fri, 23 Oct 2020 10:51:03 -0400 From: Tom Lane To: Stephen Frost cc: Heikki Linnakangas , Ian Lawrence Barwick , pgsql-hackers Subject: Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour In-reply-to: <20201023141211.GH16415@tamriel.snowman.net> References: <20201023134611.GG16415@tamriel.snowman.net> <145522.1603461363@sss.pgh.pa.us> <20201023141211.GH16415@tamriel.snowman.net> Comments: In-reply-to Stephen Frost message dated "Fri, 23 Oct 2020 10:12:11 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <147811.1603464663.1@sss.pgh.pa.us> Date: Fri, 23 Oct 2020 10:51:03 -0400 Message-ID: <147812.1603464663@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Stephen Frost writes: > We do need to decide at what point we're going to move forward pg_dump's > oldest server version support. I'm not really in a big hurry to move it forward at all. There were good solid reasons to drop support for pre-schema and pre-pg_depend servers, because of the messy kluges pg_dump had to implement to provide only-partial workarounds for those lacks. But I don't see comparable reasons or code savings that we'll get from dropping later versions. There is an argument for dropping support for server versions that fail to build anymore with modern toolchains, since once that happens it becomes difficult to test, unless you have old executables already laying around. But I don't think we're at that point yet for 8.0 or later. (I rebuilt 7.4 and later when I updated my workstation to RHEL8 a few months ago, and they seem fine, though I did use -O0 out of fear of -faggressive-loop-optimizations bugs for anything before 8.2.) But anyway, this was about documentation not code. What I'm wondering about is when to drop things like, say, this bit in the regex docs: Two significant incompatibilities exist between AREs and the ERE syntax recognized by pre-7.4 releases of PostgreSQL: (etc etc) Seems like we could have gotten rid of that by now, but when exactly does it become fair game? And can we have a non-ad-hoc process for getting rid of such cruft? regards, tom lane