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 1h9uJm-0004Y6-7X for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Mar 2019 16:25:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h9uJk-0002r9-Rw for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Mar 2019 16:25:20 +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 1h9uJk-0002r1-Jj for pgsql-hackers@lists.postgresql.org; Fri, 29 Mar 2019 16:25:20 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h9uJi-0003wX-Fw for pgsql-hackers@lists.postgresql.org; Fri, 29 Mar 2019 16:25:20 +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 x2TGP0xj019518; Fri, 29 Mar 2019 12:25:00 -0400 From: Tom Lane To: Andres Freund cc: Christoph Berg , Tatsuo Ishii , andreas@proxel.se, tomas.vondra@2ndquadrant.com, eldmannen@gmail.com, mark.kirkwood@catalyst.net.nz, michael@paquier.xyz, chris.travers@adjust.com, alvherre@2ndquadrant.com, euler@timbira.com.br, rjuju123@gmail.com, pgsql-hackers@lists.postgresql.org Subject: Re: PostgreSQL pollutes the file system In-reply-to: <20190329155121.5zyoahgh4i2r4ayl@alap3.anarazel.de> References: <20190327142657.GC17983@development> <375ea28a-2e8c-9954-66b1-bd0a3ff657f5@proxel.se> <18182.1553697687@sss.pgh.pa.us> <20190329.100407.1159785913847835944.t-ishii@sraoss.co.jp> <20190329152557.GI20294@msg.df7cb.de> <24256.1553874086@sss.pgh.pa.us> <20190329155121.5zyoahgh4i2r4ayl@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Fri, 29 Mar 2019 08:51:21 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19516.1553876700.1@sss.pgh.pa.us> Date: Fri, 29 Mar 2019 12:25:00 -0400 Message-ID: <19517.1553876700@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > On 2019-03-29 11:41:26 -0400, Tom Lane wrote: >> Or perhaps better, allow pg_ctl to grow new subcommands for those >> tasks? > We'd need to be careful to somehow delineate commands that need access > to the data directory / run locally on the server from the ones that > just needs a client connection. Hmm, that's a good point: to put it in terms that make sense to a packager, it'd no longer be clear whether pg_ctl belongs in the server package or the client package. I'm still not thrilled with wedging in these things as options to psql though: its command line semantics are overly complicated already, when you consider things like multiple -c and -f options. I mean, somebody might think it's a feature to be able to do psql --createuser alice --createuser bob -c 'some command' -f somefile but I don't. Maybe if we want to merge these things into one executable, it should be a new one. "pg_util createrole bob" ? regards, tom lane