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 1h6ffc-0002SX-FP for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 18:10:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6ffb-0001VM-6P for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 18:10:31 +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 1h6ffa-0001S4-SM for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2019 18:10:30 +0000 Received: from mimolette.dalibo.net ([212.85.157.144] helo=mail.dalibo.com) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6ffY-0004XL-QK for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2019 18:10:30 +0000 Received: from firost (155.255.88.92.rev.sfr.net [92.88.255.155]) by mail.dalibo.com (Postfix) with ESMTPSA id A740F2C03D8; Wed, 20 Mar 2019 19:10:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1553105427; bh=lp0PK5cr70bDTrCHXOlQFWUPWAS+tl+0420IQZenZQ0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=UJUAyOXmhdPXAu6cbRKCRIoMmm305WMvDT12l33F2vM/nBl93azcZslk4T5KGD9KQ M15aR5Q1xxw8E+Pl6oev9b7cTxHVxYZ23sq77q599iZ5SIlp5wzZTSMTdNQVFFWR9f f3OINkvngb3U/eL+ow7KmAgwnU05CVk2/w3LT0Nk= Date: Wed, 20 Mar 2019 19:10:25 +0100 From: Jehan-Guillaume de Rorthais To: Tom Lane Cc: Julien Rouhaud , Euler Taveira , Tatsuo Ishii , chris.travers@adjust.com, Andreas Karlsson , eldmannen@gmail.com, PostgreSQL Hackers Subject: Re: PostgreSQL pollutes the file system Message-ID: <20190320191025.22e3a5c1@firost> In-Reply-To: <13632.1553104615@sss.pgh.pa.us> References: <7b9b6804-1575-3502-d9c9-91d324c913bd@proxel.se> <29226.1553091573@sss.pgh.pa.us> <20190320.233927.1093147102517606462.t-ishii@sraoss.co.jp> <13632.1553104615@sss.pgh.pa.us> Organization: Dalibo MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 20 Mar 2019 13:56:55 -0400 Tom Lane wrote: > Julien Rouhaud writes: > > On Wed, Mar 20, 2019 at 6:25 PM Euler Taveira > > wrote: > >> createdb, dropdb, createuser, dropuser, reindexdb are binaries that > >> confuse most newbies. Which tool is theses binaries from? The names > >> does not give a hint. How often those confusing name tools are used? > > > initdb is probably an order of magnitude worse name than all of these. > > Meh. The ones with "db" in the name don't strike me as mortal sins; > even if you don't recognize them as referring to a "database", you're > not likely to guess wrongly that you know what they do. The two that > seem the worst to me are createuser and dropuser, which not only have > no visible connection to "postgres" or "database" but could easily > be mistaken for utilities for managing operating-system accounts. > > We managed to get rid of createlang and droplang in v10, and there > hasn't been that much push-back about it. So maybe there could be > a move to remove createuser/dropuser? Or at least rename them to > pg_createuser and pg_dropuser. If you rename them, rename as pg_createrole and pg_droprole :) I teach people not to use "CREATE USER/GROUP", but each time I have to tell them "Yes, we kept createuser since 8.1 where roles has been introduced for backward compatibility. No, there's no createrole". ++