Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fLKUn-0001pS-K9 for pgsql-hackers@arkaria.postgresql.org; Wed, 23 May 2018 03:31:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fLKUm-00069o-3P for pgsql-hackers@arkaria.postgresql.org; Wed, 23 May 2018 03:31:24 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1fLKUl-00069e-SL for pgsql-hackers@lists.postgresql.org; Wed, 23 May 2018 03:31:23 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fLKUe-0002Ew-GB for pgsql-hackers@postgresql.org; Wed, 23 May 2018 03:31:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w4N3V8VP005494; Tue, 22 May 2018 23:31:08 -0400 From: Tom Lane To: Bruce Momjian cc: PostgreSQL-development Subject: Re: Postgres 11 release notes In-reply-to: <20180523010258.GC12538@momjian.us> References: <28511.1526653692@sss.pgh.pa.us> <20180523010258.GC12538@momjian.us> Comments: In-reply-to Bruce Momjian message dated "Tue, 22 May 2018 21:02:58 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5492.1527046268.1@sss.pgh.pa.us> Date: Tue, 22 May 2018 23:31:08 -0400 Message-ID: <5493.1527046268@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Bruce Momjian writes: > On Fri, May 18, 2018 at 10:28:12AM -0400, Tom Lane wrote: >> While we're all griping about omissions from the release notes ... >> I think you should have documented that we fixed plpgsql to cope >> (or cope better, at least) with intrasession changes in the rowtypes >> of composite-type variables. > It was fixed in this commit, right? > commit 4b93f57999a2ca9b9c9e573ea32ab1aeaa8bf496 That was the main one, anyway. regards, tom lane