| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| 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-29 18:30:29 |
| Message-ID: | aQJdRajMMVrSx1B_@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 13, 2025 at 10:22:53PM +0200, Christoph Berg 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.
The fact is is called libpq --- Post-QUEL, and not libpg, supports your
analysis. ;-)
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2025-10-29 18:47:02 | Re: PG18 GIN parallel index build crash - invalid memory alloc request size |
| Previous Message | Robert Haas | 2025-10-29 18:29:45 | Re: apply_scanjoin_target_to_paths and partitionwise join |