Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q4qcd-0006W6-BV for pgsql-bugs@arkaria.postgresql.org; Thu, 01 Jun 2023 22:18:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q4qcb-00071U-PM for pgsql-bugs@arkaria.postgresql.org; Thu, 01 Jun 2023 22:18:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q4qcb-00071K-Gr for pgsql-bugs@lists.postgresql.org; Thu, 01 Jun 2023 22:18:17 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q4qcY-00397m-MJ for pgsql-bugs@lists.postgresql.org; Thu, 01 Jun 2023 22:18:16 +0000 Received: from pro.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 351MI9oT3250711; Thu, 1 Jun 2023 18:18:09 -0400 From: Tom Lane To: Bruce Momjian cc: bzm@2bz.de, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17957: psql-16beta1 \df+ does not show the function body In-reply-to: References: <17957-e1db8b1c15af444a@postgresql.org> Comments: In-reply-to Bruce Momjian message dated "Thu, 01 Jun 2023 15:23:12 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <48276.1685657889.1@sss.pgh.pa.us> Date: Thu, 01 Jun 2023 18:18:09 -0400 Message-ID: <48277.1685657889@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bruce Momjian writes: > On Thu, Jun 1, 2023 at 05:57:19PM +0000, PG Bug reporting form wrote: >> The release notes do not mention \df+. > We had this commit in PG 16: > Show "internal name" not "source code" in psql's \df+ command. > I didn't think anyone would mind the change so I didn't document it in > the release notes --- should I? I think it needs to be mentioned, since it's a nontrivial user-visible behavioral change. I'm not sure it's a compatibility item, but it ought to be there somewhere. regards, tom lane