Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ipZbG-0007DS-Ld for pgsql-docs@arkaria.postgresql.org; Thu, 09 Jan 2020 15:19:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ipZbF-0002XK-2F for pgsql-docs@arkaria.postgresql.org; Thu, 09 Jan 2020 15:19:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ipZbE-0002XD-QV for pgsql-docs@lists.postgresql.org; Thu, 09 Jan 2020 15:19:52 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ipZbB-0001ul-DG for pgsql-docs@lists.postgresql.org; Thu, 09 Jan 2020 15:19:52 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E65CF21C57; Thu, 9 Jan 2020 10:19:46 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Thu, 09 Jan 2020 10:19:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=/i13ndBOj67DHi4U//uUXJ7o7tFwOf0u3BRSq7kuP RE=; b=FlMBcijqT9NY1RVUQxCWzvLsXG0TO3Rq7jbbfipA7nnwQuWPwvgFuSYsu s7f6pT8cP1i6Jdn0xB7WAGLzWiRyJHC705tnpH8ViSNsXNL6e5aLYpgbq+BORgeZ u8HRZQBjkhFu/tBynbzW51cQtAiNugwz1XMp1pL0UbgzDLmpRU7o7FmHI4RMGSBj rGR7CsU/TiTr8poVhFo2aGnAUcGv9yvBOEeKU6iP8Xlzq7XoLnl6zMaijgwejsbr iL/JY1vZq0He2he3a2ZQVVp/P463itn7QX5bdDSPRBSKOiaRJr33NKS5sSci3gCp rT2Nq1bcJqTAmqzGgzIUmZGIZ2sLg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdeiuddggedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuffhomhgrihhnpedvnhguqhhurggurhgrnhhtrdgt ohhmnecukfhppeelfedrvdegfedrudekjedrudeggeenucfrrghrrghmpehmrghilhhfrh homhepphgvthgvrhdrvghishgvnhhtrhgruhhtsedvnhguqhhurggurhgrnhhtrdgtohhm necuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from april.pezone.net (p5df3bb90.dip0.t-ipconnect.de [93.243.187.144]) by mail.messagingengine.com (Postfix) with ESMTPA id F1C6E3060783; Thu, 9 Jan 2020 10:19:45 -0500 (EST) Subject: Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes To: Magnus Hagander References: <54c208b9-7e2c-6211-0ba0-ffb0429cf20b@2ndquadrant.com> <2cfbd3fe-85ef-d53b-53db-d93fbfe9f578@2ndquadrant.com> Cc: Vik Fearing , Pg Docs From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Thu, 9 Jan 2020 16:19:44 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-01-03 11:00, Magnus Hagander wrote: > On 2019-12-30 00:03, Vik Fearing wrote: > > Following a complaint on IRC about the dearth of information on > how to > > migrate to a new major version in the release notes, the attached > > trivial patch was determined to be sufficient for the OP. > > > > This patch applies to REL_12_STABLE.  I don't know how far it > should be > > backpatched (the OP was trying to upgrade to v10), and I didn't > see any > > place to put it for 13 and future versions. > > I think this change is sensible.  But to what extent do we want to edit > around in old release notes?  Should we just keep it for PG13? > > > I think it makes sense to backpatch it. Lots of people still upgrade to > at least 12 and 11, and that's a likely place for them to start reading. > And if we're already covering 12 and 11, it is probably no big extra > effort to do other supported branches as well. Committed to 12, 11, 10. After that the patch didn't apply anymore and nobody should be upgrading to that anyway. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services