Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pp9CF-0003Ds-Sa for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Apr 2023 14:54:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pp9CE-0000iG-PK for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Apr 2023 14:54:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pp9CE-0000i6-FG for pgsql-hackers@lists.postgresql.org; Wed, 19 Apr 2023 14:54:10 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pp9CC-003qaE-1U for pgsql-hackers@lists.postgresql.org; Wed, 19 Apr 2023 14:54:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 33JEs5Y82977471; Wed, 19 Apr 2023 10:54:05 -0400 From: Tom Lane To: Jim Jones cc: Ken Kato , pgsql-hackers@lists.postgresql.org Subject: Re: Tab completion for GRANT MAINTAIN In-reply-to: References: <6afe7712991882a864d6d10003264e7c@oss.nttdata.com> Comments: In-reply-to Jim Jones message dated "Wed, 19 Apr 2023 13:50:30 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2977469.1681916045.1@sss.pgh.pa.us> Date: Wed, 19 Apr 2023 10:54:05 -0400 Message-ID: <2977470.1681916045@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jim Jones writes: > On 18.04.23 11:08, Ken Kato wrote: >> I found that GRANT MAINTAIN is not tab-completed with ON, so here is a >> patch. > I've marked the CF entry as "ready for committer" Yup, clearly an oversight. Pushed. (One could wish that it didn't take touching three or so places in tab-complete.c to add a privilege, especially when a naive hacker might think he was done after touching Privilege_options_of_grant_and_revoke. I didn't see any easy way to improve that situation though.) regards, tom lane