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 1rknJd-00FQjs-4y for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Mar 2024 15:48:21 +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 1rknJb-0018Xl-Lb for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Mar 2024 15:48:20 +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 1rknJa-0018Xd-Ih for pgsql-hackers@lists.postgresql.org; Thu, 14 Mar 2024 15:48:19 +0000 Received: from fhigh5-smtp.messagingengine.com ([103.168.172.156]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rknJS-004UNI-6k for pgsql-hackers@postgresql.org; Thu, 14 Mar 2024 15:48:17 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 4E1831140119; Thu, 14 Mar 2024 11:48:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 14 Mar 2024 11:48:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm3; t=1710431290; x=1710517690; bh=sOr/mOCLKF6UonD3aCDMxnmqAB7K1OpI utuwswcAbmQ=; b=GqerLVxdDk5tVyHvW/QMjqNrNrjd8k+pCLslNet46pHhkxDW IriL8paDNvsJWs/1XkqoSXg7GL7Wp3qOB0d2ETyZcvxr9qWVMLMRNzI9G1hKqjgF IIdU0Q8IXAjYxDoG8DuRbtjwr/N310rpKSgkZ5iEOvYVpIau2aDEHAlZ47pkL+mR qrWnRFZ3LTfJLnl68fIPa8IWXBDKi5dxRfghl66ZNSTzhrE37tiRu1+SNRASR2Q0 t2hjWpCmi3s7Q0FUmG4SBuXy4QqHG9Y3sdE5jrC6RbVJtqB3kFV4aJbO8cTh7vJJ zp0El135qAAqhXXDFm5smt5ALXU5kJCETzVvmw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1710431290; x= 1710517690; bh=sOr/mOCLKF6UonD3aCDMxnmqAB7K1OpIutuwswcAbmQ=; b=k z6Rm3S0t2k597twtGAaAX7O+IMSqCJ7s6tcVAHZf55aeDXRODgvCUKi+D+cVfGr6 tmrmhW/BF692UGNCd1NtmFxu3tvkYgcTYRj+cEpHYg7do+bAwzBNEgxY9r+YfSru k+z4bVH0ZbA9MEiURgGtuasFdsTPk6x5Fc7zbqUknkvjRhHDPUuPTdiE4BBj2eEk +hRzcwzCXKpIIr67TkNkDyxjL93aci07+qoJioZZ5kUCHSfdAtTr1LtxKpSH0un+ yXa4PcC0xzkn+4zFWOfF4jUXrKE979HUWrf6U8VhQisGLu7nd5MXEhlJBe1jcyox yBt5PvumyQyfMf3/0Br4A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrjeejgdejkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthejredttddvjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhgqe enucggtffrrghtthgvrhhnpefgjedthfekfedtuefgieelheetleejgefhueeltdfhueet vdffudekfeejhfegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 14 Mar 2024 11:48:08 -0400 (EDT) Message-ID: Date: Thu, 14 Mar 2024 16:48:07 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Reports on obsolete Postgres versions Content-Language: en-US To: Bruce Momjian , Jeremy Schneider Cc: Daniel Gustafsson , Michael Banck , Nathan Bossart , PostgreSQL Hackers References: <20240311211204.GA1786481@nathanxps13> <65f02a88.170a0220.805a4.01ff@mx.google.com> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 13.03.24 18:12, Bruce Momjian wrote: > On Wed, Mar 13, 2024 at 09:21:27AM -0700, Jeremy Schneider wrote: >> It's not just roadmaps and release pages where we mix up these terms >> either, it's even in user-facing SQL and libpq routines: both >> PQserverVersion and current_setting('server_version_num') return the >> patch release version in the numeric patch field, rather than the >> numeric minor field (which is always 0). >> >> In my view, the best thing would be to move toward consistently using >> the word "patch" and moving away from the word "minor" for the >> PostgreSQL quarterly maintenance updates. > > I think "minor" is a better term since it contrasts with "major". We > don't actually supply patches to upgrade minor versions. There are potentially different adjectives that could apply to "version" and "release". The version numbers can be called major and minor, because that just describes their ordering and significance. But I do agree that "minor release" isn't quite as clear, because one could also interpret that as "a release, but a bit smaller this time". (Also might not translate well, since "minor" and "small" could translate to the same thing.) One could instead, for example, describe those as "maintenance releases": "Are you on the latest maintenance release? Why not? Are you not maintaining your database?" That carries much more urgency than the same with "minor". A maintenance release corresponds to an increase in the minor version number. It's still tied together, but has different terminology. The last news item reads: "The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL" which has no urgency, but consider "The PostgreSQL Global Development Group has published maintenance releases to all supported versions of PostgreSQL"