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 1h6c2I-0006T1-Mj for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 14:17:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6c2H-0007o5-EX for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 14:17:41 +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 1h6c2H-0007ny-7E for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2019 14:17:41 +0000 Received: from p3plsmtpa06-06.prod.phx3.secureserver.net ([173.201.192.107]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6c2D-0001CK-Sk for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2019 14:17:40 +0000 Received: from [192.168.111.168] ([107.141.18.75]) by :SMTPAUTH: with ESMTPSA id 6c29hB635qx2o6c29h0XFL; Wed, 20 Mar 2019 07:17:34 -0700 Subject: Re: PostgreSQL pollutes the file system To: pgsql-hackers@lists.postgresql.org References: <7b9b6804-1575-3502-d9c9-91d324c913bd@proxel.se> From: Chris Howard Message-ID: <1813bb47-ff0c-6d19-7e27-abd5688719a8@elfpen.com> Date: Wed, 20 Mar 2019 09:17:29 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CMAE-Envelope: MS4wfEVI7KCe2xSbT3CXynqdwGsmbNjWj3SajdvPbYKH9jUs3lSdOZ+LYTqSgVkVPNTG6YUOlf6JE5/hdtV2W+5R0FjSfToT0RiN8vODtHuhSXn7CNqC6Cqd ZrjUcTcpPfp8pcYXLFhn/fGyPnfkcVugQbsQsatR/UL/ADTbgF6cSLH6oCSq1/IVropkoEFq3zA4EA== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Another pattern is to have a separate bin path for various software packages:  /opt/postgres/bin  for example. That doesn't directly answer "what is createdb?" but it does give a quicker indication via the 'which' command. On 3/20/19 5:43 AM, Fred .Flintstone wrote: > It seems nothing came out of the discussion in 2008. > I feel the topic should be revisited. > > I am in favor of doing so too. The deprecation cycle could involve > symlinks for a brief period of time or a couple of versions. > > Yes, the wrapper script approach is used by Git as well as the "dotnet" command. > The wrapper script addition doesn't mean executing the commands > directly without the wrapper won't be possible. So one doesn't exclude > the other. > It would be a welcome addition. > > On Wed, Mar 20, 2019 at 11:05 AM Andreas Karlsson wrote: >> On 3/19/19 11:19 AM, Fred .Flintstone wrote: >>> PostgreSQL pollutes the file system with lots of binaries that it is >>> not obvious that they belong to PostgreSQL. >>> >>> Such as "/usr/bin/createdb", etc. >>> >>> It would be better if these files were renamed to be prefixed with >>> pg_, such as pg_createdb. >>> Or even better postgresql-createdb then be reachable by through a >>> "postgresql" wrapper script. >> Hi, >> >> This topic has been discussed before e.g. in 2008 in >> https://www.postgresql.org/message-id/47EA5CC0.8040102%40sun.com and >> also more recently but I cannot find it in the archives right now. >> >> I am personally in favor of renaming e.g. createdb to pg_createdb, since >> it is not obvious that createdb belongs to PostgreSQL when reading a >> script or looking in /usr/bin, but we would need a some kind of >> deprecation cycle here or we would suddenly break tons of people's scripts. >> >> And as for the git-like solution with a wrapper script, that seems to be >> the modern way to do things but would be an even larger breakage and I >> am not convinced the advantage would be worth it especially since our >> executables are not as closely related and consistent as for example git's. >> >> Andreas > >