Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aAJcV-0005yp-J7 for pgsql-hackers@arkaria.postgresql.org; Sat, 19 Dec 2015 15:40:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aAJcU-0005i0-3H for pgsql-hackers@arkaria.postgresql.org; Sat, 19 Dec 2015 15:40:30 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aAJbB-00046D-T7 for pgsql-hackers@postgresql.org; Sat, 19 Dec 2015 15:39:10 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aAJb9-0002eE-H8 for pgsql-hackers@postgresql.org; Sat, 19 Dec 2015 15:39:08 +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 tBJFctPV002548; Sat, 19 Dec 2015 10:38:55 -0500 From: Tom Lane To: Michael Paquier cc: Thomas Munro , Kyotaro HORIGUCHI , Alvaro Herrera , Jeff Janes , PostgreSQL mailing lists Subject: Re: Making tab-complete.c easier to maintain In-reply-to: References: <20151217.150633.216859242.horiguchi.kyotaro@lab.ntt.co.jp> <1851.1450471370@sss.pgh.pa.us> Comments: In-reply-to Michael Paquier message dated "Sat, 19 Dec 2015 19:11:18 +0900" Date: Sat, 19 Dec 2015 10:38:55 -0500 Message-ID: <2547.1450539535@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Michael Paquier writes: > On Sat, Dec 19, 2015 at 5:42 AM, Tom Lane wrote: >> 2. Why does MatchAnyExcept use "'" as the inversion flag, rather than >> say "!" or "~" ? Seems pretty random. > Actually, "'" is not that much a good idea, no? There could be single > quotes in queries so there is a risk of interfering with the > completion... What do you think would be good candidates? "?", "!", > "#" or "&"? We don't care whether the character appears in queries; it only matters that it not be something we'd need to use in patterns. My inclination is to use "!". regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers