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 1ifq62-0005K4-V9 for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Dec 2019 18:55:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ifq5z-0002v1-Pa for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Dec 2019 18:55:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ifq5z-0002ut-6H for pgsql-hackers@lists.postgresql.org; Fri, 13 Dec 2019 18:55:23 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ifq5r-0006tc-Lu for pgsql-hackers@lists.postgresql.org; Fri, 13 Dec 2019 18:55:21 +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 xBDIt7qP017622; Fri, 13 Dec 2019 13:55:07 -0500 From: Tom Lane To: Robert Haas cc: Alvaro Herrera , PostgreSQL Hackers , steven.winfield@cantabcapital.com Subject: Re: BUG #16059: Tab-completion of filenames in COPY commands removes required quotes In-reply-to: <17379.1576082091@sss.pgh.pa.us> References: <20191211150637.GA21159@alvherre.pgsql> <15389.1576079550@sss.pgh.pa.us> <17379.1576082091@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Wed, 11 Dec 2019 11:34:51 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17620.1576263307.1@sss.pgh.pa.us> Date: Fri, 13 Dec 2019 13:55:07 -0500 Message-ID: <17621.1576263307@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > Robert Haas writes: >> On Wed, Dec 11, 2019 at 10:52 AM Tom Lane wrote: >>> I think it's Debian's problem, not ours, if that doesn't work. It is >>> not unreasonable for a package to probe existence of a library function >>> at configure time. It's up to them to make sure that the headers match >>> the actual library. >> That seems like an unhelpful attitude. Debian is a mainstream >> platform, and no doubt feels that they have important reasons for what >> they are doing. Actually, this argument is based on a false premise anyhow. I took a look into Debian's source package, and AFAICS they are not doing anything as weird as a run-time substitution. They are just filling the build environment with libedit-dev not libreadline-dev. So that is certainly a supported configuration from our side, and if there is any header-to-library discrepancy then it's just a simple bug in the libedit package. (Maybe at one time they were doing something weird; I didn't look back further than the current sources for PG 12.) regards, tom lane