Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rrYVA-001HzL-A0 for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Apr 2024 07:24:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rrYV8-005cuU-OJ for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Apr 2024 07:24:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rrYV8-005cuL-Et for pgsql-hackers@lists.postgresql.org; Tue, 02 Apr 2024 07:24:11 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rrYV6-0006Jh-Bw for pgsql-hackers@postgresql.org; Tue, 02 Apr 2024 07:24:09 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id B948D3008355 for ; Tue, 2 Apr 2024 09:24:05 +0200 (CEST) Received: from s981.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id A8C8E2E28028; Tue, 2 Apr 2024 09:24:05 +0200 (CEST) Received: from s473.loopia.se (unknown [172.22.191.5]) by s981.loopia.se (Postfix) with ESMTP id A651322B178B; Tue, 2 Apr 2024 09:24:05 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.21 X-Spam-Level: X-Spam-Status: No, score=-1.21 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=disabled Authentication-Results: s473.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=yesql.se Received: from s899.loopia.se ([172.22.191.6]) by s473.loopia.se (s473.loopia.se [172.22.190.13]) (amavisd-new, port 10024) with UTF8LMTP id cYJRjvgnKuk5; Tue, 2 Apr 2024 09:24:05 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s899.loopia.se (Postfix) with ESMTPSA id 121B62C8BAB6; Tue, 2 Apr 2024 09:24:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1712042645; bh=MpLDkcn8ZOkV5WlCpg/hufWJ2qYOun/Ffl/3QXrHiZQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=q2GF6HSHJdEPjIEYNitu+G+ENnLciXg3ZuD6x3Lvpkm5BKWk4gSRzC3MWfczgsnUn Ur3j3Fw3A5Ev+11S07mIC6eUGtVPxzQud4rs2/LOpmBxsYkMWgMH5aXONWA+pLvn6x FSCpdvFFI5NaqzDR2pek7QSA6mUn8It5sDE6/ZUPIzNurk763SG8n3ePLKefw/rdAg TomzKqr9hf2WfnXE0SN/nEKcf0VxSmS6aKEJpmJ1URjkYtZkKpv6I1yBBsxRuEDSPM JTHd/TGgcx3MOiK8iOxhQi3xerVGRIHxY8Te9RP2hWYr+SXDTEaSG1QhPmz/L22pY9 Q5z0Z6sjcJFwA== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) Subject: Re: Reports on obsolete Postgres versions From: Daniel Gustafsson In-Reply-To: Date: Tue, 2 Apr 2024 09:24:04 +0200 Cc: Robert Treat , Jeremy Schneider , Michael Banck , Nathan Bossart , PostgreSQL Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <7C1994C7-8316-40C0-931F-FE2DBEEF2FC2@yesql.se> References: <20240311211204.GA1786481@nathanxps13> <65f02a88.170a0220.805a4.01ff@mx.google.com> To: Bruce Momjian X-Mailer: Apple Mail (2.3696.120.41.1.4) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 2 Apr 2024, at 00:56, Bruce Momjian wrote: > I ended up writing the attached doc patch. I found that some or our > text was overly-wordy, causing the impact of what we were trying to = say > to be lessened. We might want to go farther than this patch, but I > think it is an improvement. Agreed, this is an good incremental improvement over what we have. > I also moved the text to the bottom of the section +1 A few small comments: +considers performing minor upgrades to be less risky than continuing to +run superseded minor versions. I think "superseded minor versions" could be unnecessarily complicated = for non-native speakers, I consider myself fairly used to reading english = but still had to spend a few extra (brain)cycles parsing the meaning of it in this context. + We recommend that users always run the latest minor release associated Or perhaps "current minor release" which is the term we use in the table = below on the same page? -- Daniel Gustafsson