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 1h6fgr-0002ZV-Sn for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 18:11:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6fgq-0005DJ-Lk for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 18:11:48 +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 1h6fgq-00057b-95 for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2019 18:11:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6fgn-0004KN-N2 for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2019 18:11:46 +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 x2KIBhp6014137; Wed, 20 Mar 2019 14:11:43 -0400 From: Tom Lane To: "Fred .Flintstone" cc: Chris Travers , Andreas Karlsson , Postgres hackers Subject: Re: PostgreSQL pollutes the file system In-reply-to: References: <7b9b6804-1575-3502-d9c9-91d324c913bd@proxel.se> <29226.1553091573@sss.pgh.pa.us> Comments: In-reply-to "Fred .Flintstone" message dated "Wed, 20 Mar 2019 16:30:33 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14135.1553105503.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 20 Mar 2019 14:11:43 -0400 Message-ID: <14136.1553105503@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "Fred .Flintstone" writes: > Even just creating symlinks would be a welcome change. > So the real binary is pg_foo and foo is a symoblic link that points to p= g_foo. > Then at least I can type pg_ and use tab auto-completion to find > everything related to PostgreSQL. You'd miss psql. I think the odds of renaming psql are not distinguishable from zero: whatever arguments you might want to make about, say, renaming initdb perhaps not affecting too many scripts are surely not going to fly for psql. So that line of argument isn't too convincing. regards, tom lane