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 1saJx5-007yb0-Qh for pgsql-general@arkaria.postgresql.org; Sat, 03 Aug 2024 18:58:03 +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 1saJx4-006cqD-4z for pgsql-general@arkaria.postgresql.org; Sat, 03 Aug 2024 18:58:02 +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 1saJx3-006cpr-Pd for pgsql-general@lists.postgresql.org; Sat, 03 Aug 2024 18:58:01 +0000 Received: from mail-oi1-x229.google.com ([2607:f8b0:4864:20::229]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1saJx1-002uFO-6A for pgsql-general@lists.postgresql.org; Sat, 03 Aug 2024 18:58:00 +0000 Received: by mail-oi1-x229.google.com with SMTP id 5614622812f47-3daf0e73a5bso6214486b6e.0 for ; Sat, 03 Aug 2024 11:57:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722711478; x=1723316278; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0vDHHRQmTte7QAVsNgF3VNawsaC/ukxkxXPAVj+KfZg=; b=UNqDwiA4IHMgvU8M7s53Lt7oVBvklvheiw1vxtp8nUt/2j03JDpAeJBVbl2qIJkcSz zd+Y2dOb5+7em1W1PMqisSf8+tzdtnz2nrDy1BMgK3XF/nwz5W3+c56Mrq4qkIV83C3g J6nKR5gra6qkHFDUbx/9+h2YXr8LI5FfmijEIR8R2EWYMtRUwqG6+SO8bdOozJ7WgQ9y ZNSQhQmD4+I3HY/DChRD4PcvAJX54soAKKcCGgPYvXkbeWpEKj4xop6B6fKVR8Gx/6+A ZbctAajRuXyMn+zia5NNDLsV9i4R2EBlXJqYulcBX4PUeb9f7MHaIeI9CDxd+liqb6DJ bQ8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722711478; x=1723316278; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0vDHHRQmTte7QAVsNgF3VNawsaC/ukxkxXPAVj+KfZg=; b=fFo+3VI8K6YBI5c2Ep6ommQJNB3ARGQeZgFFnM8NPPMfGQt4T4YDEWKQ1xmjr8ho2C P3XzZTiiEncAf/rIbyst2Dz9KqUn+PIV01WncOpP6lJrfRHHgqki4KIkpAioe36cebbn DSmaunRiOXAbub1R5ElgKu9SeE6RViyjgaHvYMGiQYt7U9sXGRYDngAxCZaiSk9CqaK1 YNJib8orLhDahFy+hNkT00UZkzchfCNC0QPQZvHAOs59vEHQ/P2PRJwjKG5CwJPTF1S4 7U9QWNxU04TEuZ3Ixa4f7gk+w9x6+ukaZBbSqOV2sLZuq1WLQKcUYdNi+Fm04IemUZ0l R4qQ== X-Gm-Message-State: AOJu0YxUeAuYe3tR5/5dQqRRP4/iHFTw0mTVO5vRXynRCVFI4l6seO00 s0U8VNdFUlAGc0pP9sU7bPR7/kNhu0mJzJGCYYs6TOHj9kqhTfpubVV89FUM/bGybseutWDHCvP X2eyd7coUjpBFy29Pc1hPBxaODIknADUV X-Google-Smtp-Source: AGHT+IGEPXssVmTmb8lVrA0NmLT609Nh7LvuLGkMp3LoDNKzhUCZ1t1XyiQrJPVotyMm81YfnY6nAuEUK28HvbPdcto= X-Received: by 2002:a05:6870:9721:b0:229:f022:ef83 with SMTP id 586e51a60fabf-26891ecdd8cmr8914261fac.43.1722711478534; Sat, 03 Aug 2024 11:57:58 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:6c93:0:b0:557:c384:fb61 with HTTP; Sat, 3 Aug 2024 11:57:57 -0700 (PDT) In-Reply-To: <87jzgxjv9x.fsf@metapensiero.it> References: <87jzgxjv9x.fsf@metapensiero.it> From: "David G. Johnston" Date: Sat, 3 Aug 2024 11:57:57 -0700 Message-ID: Subject: Re: Some links to "previous version" seem wrong To: Lele Gaifax Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000ba9e1e061ecc05ff" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ba9e1e061ecc05ff Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Saturday, August 3, 2024, Lele Gaifax wrote: > the page related to > 15.4[2] says > > Also, if you are upgrading from a version earlier than 15.1, see > Section E.7. > > Is that correct? > Yes, the wording and links are correct. If you are upgrading from 15.2 or 15.3 to 15.4 there is no =E2=80=9Csee als= o=E2=80=9D to worry about. The point of that sentence is not to provide a simple always-present link to the prior release notes. It is to warn about special update concerns if the update is not trivial. David J. --000000000000ba9e1e061ecc05ff Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Saturday, August 3, 2024, Lele Gaifax <lele@metapensiero.it> wrote:
the page related to
15.4[2] says

=C2=A0 Also, if you are upgrading from a version earlier than 15.1, see
=C2=A0 Section E.7.

Is that correct?


Yes, the wording and links are correct.
If you are upgrading from 15.2 or 15.3 to 15.4 there is no =E2= =80=9Csee also=E2=80=9D to worry about.

The point = of that sentence is not to provide a simple always-present link to the prio= r release notes.=C2=A0 It is to warn about special update concerns if the u= pdate is not trivial.

David J.

--000000000000ba9e1e061ecc05ff--