pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Adding SHOW CREATE TABLE
Date: Sat, 20 May 2023 14:19:10 -0400
Message-ID: <877833.1684606750@sss.pgh.pa.us> (raw)
In-Reply-To: <CAKFQuwbK3z2bgPk+qdB6TiKzNrYs1w1cBdxhyU4VkTbpa_s52g@mail.gmail.com>
References: <ZF6jY1vqhxfGME+b@tamriel.snowman.net>
	<CACLU5mROQewFBFXG=C6DMvEtDgGZoF9k=m_bkTJYFgSNZptUkg@mail.gmail.com>
	<1aac01a1-d9db-8048-9bfa-1e4f9bb69a03@gmail.com>
	<CACLU5mQDDhdwu4Z8aRqNrc+UDLTE+GmfZPbxn39dha5m_EUEfQ@mail.gmail.com>
	<CAM8SmLV3RcGHsnhwk9=vAdhUGnYfCQ9xUsrBdXwyKn=_9wCDLw@mail.gmail.com>
	<CACLU5mSmZ0hoCbbkGBS7X2jczC8bmP5PE+w=BC=UvAp+36AoBw@mail.gmail.com>
	<CACLU5mQmq2r6FicCXm7Rj2JbyTyDdAdTEcSFAfO6bnK7x+S6aA@mail.gmail.com>
	<ZGa6lrLlZVIarDK4@tamriel.snowman.net>
	<6afd776b-45cf-2675-0cfe-981f1c6ade1d@dunslane.net>
	<fbde7a194938f79580ef0cebb34f2b174b26b56a.camel@cybertec.at>
	<ZGkCxT614Kg4emrs@tamriel.snowman.net>
	<CAKFQuwbK3z2bgPk+qdB6TiKzNrYs1w1cBdxhyU4VkTbpa_s52g@mail.gmail.com>

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Sat, May 20, 2023 at 10:26 AM Stephen Frost <sfrost@snowman.net> 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





view thread (46+ messages)  latest in thread

Message-ID: <877833.1684606750@sss.pgh.pa.us>
Permalink:  ../877833.1684606750@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/877833.1684606750@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, sfrost@snowman.net, laurenz.albe@cybertec.at, andrew@dunslane.net, pgsql-hackers@lists.postgresql.org
  Subject: Re: Adding SHOW CREATE TABLE
  In-Reply-To: <877833.1684606750@sss.pgh.pa.us>
  References: <ZF6jY1vqhxfGME+b@tamriel.snowman.net> <CACLU5mROQewFBFXG=C6DMvEtDgGZoF9k=m_bkTJYFgSNZptUkg@mail.gmail.com> <1aac01a1-d9db-8048-9bfa-1e4f9bb69a03@gmail.com> <CACLU5mQDDhdwu4Z8aRqNrc+UDLTE+GmfZPbxn39dha5m_EUEfQ@mail.gmail.com> <CAM8SmLV3RcGHsnhwk9=vAdhUGnYfCQ9xUsrBdXwyKn=_9wCDLw@mail.gmail.com> <CACLU5mSmZ0hoCbbkGBS7X2jczC8bmP5PE+w=BC=UvAp+36AoBw@mail.gmail.com> <CACLU5mQmq2r6FicCXm7Rj2JbyTyDdAdTEcSFAfO6bnK7x+S6aA@mail.gmail.com> <ZGa6lrLlZVIarDK4@tamriel.snowman.net> <6afd776b-45cf-2675-0cfe-981f1c6ade1d@dunslane.net> <fbde7a194938f79580ef0cebb34f2b174b26b56a.camel@cybertec.at> <ZGkCxT614Kg4emrs@tamriel.snowman.net> <CAKFQuwbK3z2bgPk+qdB6TiKzNrYs1w1cBdxhyU4VkTbpa_s52g@mail.gmail.com> <877833.1684606750@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox