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 1q0RAn-0003rN-SB for pgsql-hackers@arkaria.postgresql.org; Sat, 20 May 2023 18:19:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q0RAl-0007CE-LJ for pgsql-hackers@arkaria.postgresql.org; Sat, 20 May 2023 18:19:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q0RAl-0007AI-BQ for pgsql-hackers@lists.postgresql.org; Sat, 20 May 2023 18:19:19 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q0RAi-0011zy-1Q for pgsql-hackers@lists.postgresql.org; Sat, 20 May 2023 18:19:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 34KIJA14877834; Sat, 20 May 2023 14:19:11 -0400 From: Tom Lane To: "David G. Johnston" cc: Stephen Frost , Laurenz Albe , Andrew Dunstan , pgsql-hackers@lists.postgresql.org Subject: Re: Adding SHOW CREATE TABLE In-reply-to: References: <1aac01a1-d9db-8048-9bfa-1e4f9bb69a03@gmail.com> <6afd776b-45cf-2675-0cfe-981f1c6ade1d@dunslane.net> Comments: In-reply-to "David G. Johnston" message dated "Sat, 20 May 2023 10:31:54 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <877832.1684606750.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Sat, 20 May 2023 14:19:10 -0400 Message-ID: <877833.1684606750@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > On Sat, May 20, 2023 at 10:26 AM Stephen Frost wrote: >> Clearly any client using libpq can conveniently call code which is in >> libpq. > Clearly there are clients that don't use libpq. JDBC comes to mind. Yeah. I'm also rather concerned about the bloat factor; it's hardly unlikely that this line of development would double the size of libpq, to add functionality that only a small minority of applications would use. A client-side implementation also has no choice but to cope with multiple server versions, and to figure out what it's going to do about a too-new server. Up to now we broke compatibility between libpq and server maybe once every couple decades, but it'd be once a year for this. regards, tom lane