Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iI6Tw-0001bA-E1 for pgsql-hackers@arkaria.postgresql.org; Wed, 09 Oct 2019 07:34:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iI6Tt-0006iK-Od for pgsql-hackers@arkaria.postgresql.org; Wed, 09 Oct 2019 07:33:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iI6Tt-0006iB-FE for pgsql-hackers@lists.postgresql.org; Wed, 09 Oct 2019 07:33:57 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iI6Tr-00079P-Gs for pgsql-hackers@postgresql.org; Wed, 09 Oct 2019 07:33:57 +0000 Received: from msg.df7cb.de (unknown [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 46p5Yv0kgfz3DyX; Wed, 9 Oct 2019 09:33:55 +0200 (CEST) Date: Wed, 9 Oct 2019 09:33:54 +0200 From: Christoph Berg To: Tom Lane Cc: PostgreSQL Hackers Subject: Re: pgsql: Remove pqsignal() from libpq's official exports list. Message-ID: <20191009073354.GB30556@msg.df7cb.de> Mail-Followup-To: Christoph Berg , Tom Lane , PostgreSQL Hackers References: <20191004095630.GA29119@msg.df7cb.de> <9333.1570566305@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9333.1570566305@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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