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 1inR43-0002Ql-23 for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jan 2020 17:48:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1inR41-0002Lz-RX for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Jan 2020 17:48:45 +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 1inR41-0002Ls-EB for pgsql-hackers@lists.postgresql.org; Fri, 03 Jan 2020 17:48:45 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1inR3y-0007aM-Mj for pgsql-hackers@postgresql.org; Fri, 03 Jan 2020 17:48:44 +0000 Received: from msg.df7cb.de (unknown [IPv6:2a02:908:1476:ff00:76e5:bff:fef3:7e00]) (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 47qC7X0JGjz3Dwk; Fri, 3 Jan 2020 18:48:40 +0100 (CET) Date: Fri, 3 Jan 2020 18:48:39 +0100 From: Christoph Berg To: Tom Lane Cc: PostgreSQL Hackers Subject: Re: pgsql: Add basic TAP tests for psql's tab-completion logic. Message-ID: <20200103174839.GD32629@msg.df7cb.de> Mail-Followup-To: Christoph Berg , Tom Lane , PostgreSQL Hackers References: <20200103170226.GB32629@msg.df7cb.de> <26339.1578072930@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26339.1578072930@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 2020-01-03 <26339.1578072930@sss.pgh.pa.us> > Christoph Berg writes: > > Re: Tom Lane 2020-01-03 <13708.1578059577@sss.pgh.pa.us> > >> I found out while investigating this that the libedit version shipping > >> with buster (3.1-20181209) is differently broken for the same case: > > > (Fwiw this wasn't spotted before because we have this LD_PRELOAD hack > > that replaces libedit with readline at psql runtime. > > You do? I went looking in the Debian package source repo just the > other day for some evidence that that was true, and couldn't find > any, so I concluded that it was only an urban legend. Where is that > done exactly? /usr/share/postgresql-common/pg_wrapper https://salsa.debian.org/postgresql/postgresql-common/blob/master/pg_wrapper#L129-157 > Perhaps more importantly, *why* is it done? It seems to me that it > takes a pretty fevered imagination to suppose that using libreadline Tom, claiming that things are "fevered" just because you didn't like them is not appropriate. It's not fun working with PostgreSQL when the tone is like that. > that way meets the terms of its license but just building against > the library normally would not. Certainly when I worked for Red Hat, > their lawyers did not think there was any problem with building > Postgres using both openssl and readline. I'm not starting that debate here, but Debian thinks otherwise: https://lwn.net/Articles/428111/ > The reason I'm concerned about this is that there's a patch on the > table [1] that will probably not behave nicely at all if it's > compiled against libedit headers and then executed with libreadline, > because it will draw the wrong conclusions about whether the > filename quoting hooks are available. So that hack is going to > fail on you soon, especially after I add regression testing around > the filename completion stuff ;-) Well, so far, it worked well. (The biggest problem used to be that libedit didn't have the history append function so it wasn't used even with readline, but that got implemented ~2 years ago.) Christoph