On Thu, Jun 17, 2021 at 1:16 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > We don't really add major new APIs to libpq very often, so I don't > find that too compelling. I do find it compelling that user code > shouldn't embed knowledge about "feature X arrived in version Y".
I just went and looked at how exports.txt has evolved over the years. Since PostgreSQL 8.1, every release except for 9.4 and 11 added at least one new function to libpq. That means in 14 releases we've done something that might break someone's compile 12 times. Now maybe you want to try to argue that few of those changes are "major," but I don't know how that could be a principled argument. Every new function is something someone may want to use, and thus a potential compile break. Some of those releases also changed behavior. For example, version 10 allowed multi-host connection strings and URLs. People might want to know about that sort of thing, too. -- Robert Haas EDB: http://www.enterprisedb.com
