From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Build src/port files as a library with -fPIC, and use that in li |
Date: | 2019-01-31 20:01:34 |
Message-ID: | CA+TgmoaK=2eDAjy-_VtQpbAtpEcXJM66cMAGsNcOAcZxGgyegA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Thu, Jan 31, 2019 at 2:50 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > Isn't the issue more a matter of whether it's OK to break
> > compatibility without changing SO_*_VERSION?
>
> We're breaking compatibility only if you regard pqsignal() as
> part of the advertised API, which I don't.
Well, I would agree with that if it weren't the case that binaries we
ship apparently use that API. If we say that the libraries are
API-compatible, but our own binaries don't work, our veracity is
questionable.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-01-31 20:04:04 | Re: pgsql: Build src/port files as a library with -fPIC, and use that in li |
Previous Message | Tom Lane | 2019-01-31 19:50:37 | Re: pgsql: Build src/port files as a library with -fPIC, and use that in li |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-01-31 20:04:04 | Re: pgsql: Build src/port files as a library with -fPIC, and use that in li |
Previous Message | Tom Lane | 2019-01-31 19:50:37 | Re: pgsql: Build src/port files as a library with -fPIC, and use that in li |