Re: pgsql: Remove pqsignal() from libpq's official exports list. - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: pgsql: Remove pqsignal() from libpq's official exports list.
Date
Msg-id 20191009073354.GB30556@msg.df7cb.de
Whole thread Raw
In response to Re: pgsql: Remove pqsignal() from libpq's official exports list.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Remove pqsignal() from libpq's official exports list.
List pgsql-hackers
Re: Tom Lane 2019-10-08 <9333.1570566305@sss.pgh.pa.us>
> Having said all that, if we conclude we can't break compatibility
> with this legacy code quite yet, I'd be inclined to put a
> separate, clearly-marked-as-legacy-code version of pqsignal()
> back into libpq, using the pre-9.3 SA_RESTART semantics.

That would be nice.

> But I'd like some pretty well-defined sunset time for that,
> because it'd just be trouble waiting to happen.  When are
> you going to remove 9.2 psql?

Note that this change caused breakage on the wiki.postgresql.org
infrastructure which still had an old 9.2 psql running. It wasn't
Debian's fault that it had not been upgraded yet.

But I refuse to buy the argument that I'm doing something wrong here.
Shared libraries have SONAMEs to prevent *exactly* this kind of
breakage. If you are removing symbols, bump the SONAME.

Christoph



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: dropping column prevented due to inherited index
Next
From: Dilip Kumar
Date:
Subject: Re: maintenance_work_mem used by Vacuum