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 1rkTMa-00Cxwn-Eo for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Mar 2024 18:30:05 +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 1rkTMY-00AJWT-RE for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Mar 2024 18:30:03 +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 1rkTMY-00AJTv-DN for pgsql-hackers@lists.postgresql.org; Wed, 13 Mar 2024 18:30:03 +0000 Received: from mail-pl1-x62f.google.com ([2607:f8b0:4864:20::62f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rkTMV-004KZ9-12 for pgsql-hackers@postgresql.org; Wed, 13 Mar 2024 18:30:01 +0000 Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-1dd7df835a8so1080235ad.1 for ; Wed, 13 Mar 2024 11:30:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ardentperf-com.20230601.gappssmtp.com; s=20230601; t=1710354599; x=1710959399; darn=postgresql.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=6UKWfQJY2a9Ucg7g+6n6Csl/+r3pe1zf7JxviZw8GPA=; b=fi8LjTKNTL8dKiGZyyMoGNWqbe6a91kTCZtm+mu0PKtQKn9KX2hBWorZU+AXhWLIUY fGe4XWR50MELM8zXxFs7R6ptlb2/q/YTz+96+B1VzasAAgjrF93vPsfouYw1oQQ+yjoL K9mXlJgJMNLdLjldGwWBB+W6r+Ken1qEL2TghkURkTmKj/NpMD61Lhg8bW7/6vmC03jq 5yLufoWL241RhUvPCyhooqKJKy7YceTk5+aNC+EFU4K50/5WL2pRIN3p2zx/DBdwc7VX X7q0rJ8Swnzx8qFLPXPYOvPznMkzemw8iTIyuDD6Z4VmkioEp0vGsdJxFwrg6Ju/KjPY xBPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710354599; x=1710959399; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6UKWfQJY2a9Ucg7g+6n6Csl/+r3pe1zf7JxviZw8GPA=; b=FfWDWl4lm7iqiZBF9uUE1qnltmg6vxN5VlgsayeRpPuBWgFNi3vNla5ZRHohJJfIuq rB6Nbb+o7avB5SfjY21oKCJTkjbT7j6LbC2yO6bEjgbMCfLrheCCYlZVjNoNbj9xqIvC PDMLLWGfS0SE6H09vjXTUci4MEV/FM6JkOptxSaysftKbELDbG7a8Z3O2dVSirRhJhin VDfgMcLg9X7xrEF0FMpYq7kieRak6lQheicjWsYfhutgxrDYo6IpSP/qM4NZJmnP+m42 58UlyR1G42A8efj0s4GDnaUlfFSYWe+9jLq+s6auOVcDt5r6xFaMt98IZjH08ur1wpnZ SQ4Q== X-Forwarded-Encrypted: i=1; AJvYcCWcp8zQrDgWK9THaQECMK6QOVs2SIrBJ0+6AfxyYwuB8sOTg5nGckRFmE7MbX6ok5Q/rhS0QsAarU87+X1FkwKlQ8Vwf2GL24tqoQL3 X-Gm-Message-State: AOJu0Yzu0nLq9ykKq1n5goFbUTJl4hugJwKRrx7zVGfgoOZ7yaYcRa8Q tH+WfTIKoNe0lb9tUZI4PaoEO7DSSc2y8UGYdrLQnyg6AFZ7Nd3N65H5aYyO8Q== X-Google-Smtp-Source: AGHT+IEqniSfr/or4k4PYARWQ3Vd+dKejqIj8OEdU0eEUe9icHy4MR6TeOw1KMK0klNjy12FqBl3EA== X-Received: by 2002:a17:902:ee84:b0:1dd:8ee9:62e4 with SMTP id a4-20020a170902ee8400b001dd8ee962e4mr3699960pld.39.1710354599223; Wed, 13 Mar 2024 11:29:59 -0700 (PDT) Received: from [192.168.13.251] (54-240-198-38.amazon.com. [54.240.198.38]) by smtp.gmail.com with ESMTPSA id mn13-20020a1709030a4d00b001dc96292774sm8984638plb.296.2024.03.13.11.29.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 Mar 2024 11:29:58 -0700 (PDT) Message-ID: <325f2571-aea9-4427-8fbb-b24b7103483f@ardentperf.com> Date: Wed, 13 Mar 2024 11:29:57 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Reports on obsolete Postgres versions To: Tom Lane , Robert Treat Cc: Bruce Momjian , Daniel Gustafsson , Michael Banck , Nathan Bossart , PostgreSQL Hackers References: <20240311211204.GA1786481@nathanxps13> <65f02a88.170a0220.805a4.01ff@mx.google.com> <2074093.1710354080@sss.pgh.pa.us> Content-Language: en-US From: Jeremy Schneider In-Reply-To: <2074093.1710354080@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 3/13/24 11:21 AM, Tom Lane wrote: > Robert Treat writes: >> On Wed, Mar 13, 2024 at 1:12 PM Bruce Momjian wrote: >>> On Wed, Mar 13, 2024 at 09:21:27AM -0700, Jeremy Schneider wrote: >>>> 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. > >> I tend to agree with Bruce, and major/minor seems to be the more >> common usage within the industry; iirc, debian, ubuntu, gnome, suse, >> and mariadb all use that nomenclature; and ISTR some distro's who >> release packaged versions of postgres with custom patches applied (ie >> 12.4-2 for postgres 12.4 patchlevel 2). > > Agreed, we would probably add confusion not reduce it if we were to > change our longstanding nomenclature for this. "Longstanding nomenclature"?? Before v10, the quarterly maintenance updates were unambiguously and always called patch releases I don't understand the line of thinking here Bruce started this whole thread because of "an increasing number of bug/problem reports on obsolete Postgres versions" Across the industry the word "minor" often implies a release that will be maintained, and I'm trying to point out that the change in v10 to change terminology from "patch" to "minor" actually might be part of what's responsible for the increasing number of bug reports on old patch releases, because people don't understand that patch releases are the way those bugfixes were already delivered. Just taking MySQL as an example, it's clear that a "minor" like 5.7 is a full blown release that gets separate patches from 5.6 - so I don't understand how we're making an argument it's the opposite? -Jeremy -- http://about.me/jeremy_schneider