| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: Thoughts on a "global" client configuration? |
| Date: | 2025-10-13 20:24:07 |
| Message-ID: | CA+Tgmoa8FcgiU9gx4yvD0p-d74=gP+VJAzBhjYJmTzca44_XiA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 13, 2025 at 4:22 PM Christoph Berg <myon(at)debian(dot)org> wrote:
> Re: Robert Haas
> > My theory is that they'll be even less impressed if they try to use a
> > supposedly-compatible library and it breaks a bunch of stuff, but I
> > wonder what Christoph Berg (cc'd) thinks.
>
> It would also hinder adoption of PG in more places. There are
> currently thousands of software products that link to libpq in some
> form, and it would take several years to have them all fixed if
> ABI/API compatibility were broken. Chasing the long tail there is
> hard; we get to witness that every year with upstreams that aren't
> compatible with PG18 yet. For some extensions, I'm still waiting to
> get my PG17 (or PG16!) patches merged.
So you support calling it libpq.so.5 forever, no matter how much we change?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arseniy Mukhin | 2025-10-13 20:24:44 | Re: Remove custom redundant full page write description from GIN |
| Previous Message | Christoph Berg | 2025-10-13 20:22:53 | Re: Thoughts on a "global" client configuration? |