Re: Problem linking with Release library
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Igor Korot <ikorot01@gmail.com>, "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>,
"pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2026-05-13T04:32:25Z
Lists: pgsql-general
On Tue, 2026-05-12 at 19:52 -0700, Igor Korot wrote: > There used to be a split builds - one package to build the server and another to build the client (libpq). This is no longer the case. > PostgreSQL positions itself as client-server RDBMS, so why in order to build the client I need the full blown server to download? I don't have Windows at my disposal, so I cannot investigate this, but it strikes me that you are complaining for the sake of complaining. I have never seen a client-only source download for PostgreSQL, so you always had to download the complete source. What is the problem? Does your internet connection have a problem with downloading 30MB? And if you have to build the entire server just to get the client library, what is the problem with that? Yes, it will take somewhat longer, but I don't see that as a problem unless you are building the software several times a day, which seems unlikely for a production build. It used to be that I could fit a custom-built Linux kernel on a 1.44MB rescue floppy disk. Still, I don't complain to the LKML that I can no longer do that. Yours, Laurenz Albe
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Remove MSVC scripts
- 1301c80b2167 17.0 cited