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 1gpIZI-0006OQ-2u for pgsql-hackers@arkaria.postgresql.org; Thu, 31 Jan 2019 20:04:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gpIZG-0004Dr-RL for pgsql-hackers@arkaria.postgresql.org; Thu, 31 Jan 2019 20:04:10 +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 1gpIZG-0004BM-Je for pgsql-hackers@lists.postgresql.org; Thu, 31 Jan 2019 20:04:10 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gpIZE-0008VJ-Jk for pgsql-hackers@postgresql.org; Thu, 31 Jan 2019 20:04:10 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x0VK44ix012793; Thu, 31 Jan 2019 15:04:04 -0500 From: Tom Lane To: Robert Haas cc: Christoph Berg , PostgreSQL Hackers Subject: Re: pgsql: Build src/port files as a library with -fPIC, and use that in li In-reply-to: References: <20180928115830.GC26142@msg.df7cb.de> <19404.1538140436@sss.pgh.pa.us> <20180928132013.GE26142@msg.df7cb.de> <20671.1538142538@sss.pgh.pa.us> <20190129140437.GF9860@msg.df7cb.de> <27653.1548774621@sss.pgh.pa.us> <11918.1548964237@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Thu, 31 Jan 2019 15:01:34 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12791.1548965044.1@sss.pgh.pa.us> Date: Thu, 31 Jan 2019 15:04:04 -0500 Message-ID: <12792.1548965044@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: > On Thu, Jan 31, 2019 at 2:50 PM Tom Lane wrote: >> 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. initdb hasn't depended on those libpq exports since 8.2, and it was a bug that it did so even then. regards, tom lane