From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Adding SHOW CREATE TABLE |
Date: | 2023-05-20 18:33:19 |
Message-ID: | CAOuzzgrTQ5jzg2toObrCaNWDSCSc=1V0bczK3wYr3gtW1mY4CA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Greetings,
On Sat, May 20, 2023 at 13:32 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Sat, May 20, 2023 at 10:26 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
>> > A server function can be conveniently called from any client code.
>>
>> 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.
>
Indeed … as I mentioned up-thread already.
Are we saying that we want this to be available server side, and largely
duplicated, specifically to cater to non-libpq users? I’ll put out there,
again, the idea that perhaps we put it into the common library then and
make it available via both libpq and as a server side function ..?
We also have similar code in postgres_fdw.. ideally, imv anyway, we’d not
end up with three copies of it.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Kirk Wolak | 2023-05-21 05:58:53 | Re: Adding SHOW CREATE TABLE |
Previous Message | Tom Lane | 2023-05-20 18:19:10 | Re: Adding SHOW CREATE TABLE |
From | Date | Subject | |
---|---|---|---|
Next Message | MARK CALLAGHAN | 2023-05-20 21:32:36 | Re: benchmark results comparing versions 15.2 and 16 |
Previous Message | Tom Lane | 2023-05-20 18:19:10 | Re: Adding SHOW CREATE TABLE |