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 1h98xo-0004xS-Da for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 13:51:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h98xn-0004AK-3k for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 13:51:31 +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 1h98xm-0004A7-OV for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 13:51:30 +0000 Received: from mail-wr1-x444.google.com ([2a00:1450:4864:20::444]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h98xg-0001VB-Ut for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 13:51:29 +0000 Received: by mail-wr1-x444.google.com with SMTP id y7so14544806wrn.11 for ; Wed, 27 Mar 2019 06:51:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=0FU1KHudR4NAJShDF230ZVbMC1WiT9gbx3qVekDDiWs=; b=XPF469gHe06/RE/ZDB/j1Fv+35bZax9l9326Jw2uVKjvdsvUW49jXBsVmh+Erx01os r0fqNmJQkE42L6yy/TgKrPyt2JZMJYyquDb2fDLKCw/a3ERR+e5PYeABeKOEurl7+PHr 8MQGvl2UxKO8jkuSzsiOwUSZslHp7IS3Nw5JjBd5sJYEvSHTyZhmuakRZTrC/QhOLPaI N8iYAL03YlDDJT3vinSM0R76hGCDGML7ZyplOmtUAdjBTjFFPE0fAW1O1qROJAUWWyUf hXMEOtXATpxBGqnNFu4YddbZPUOu7c1VvG/oxmy806oL3we3Te7BclQLlyoVYi65JdUr h3WQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=0FU1KHudR4NAJShDF230ZVbMC1WiT9gbx3qVekDDiWs=; b=SF7NUsjotXc2BUuCgLKos51Wm/EoNlWKOs07aYks8BMmZyqX8CXhqEIqd0Glx9mFuv nWwZeb0KcK2xzAGCTTT30Y0s02x+uSAEIbHLMn+taultPk4m50BjzW048dt+6u0FJ34w ZK8zTPhhoFljiKIRyO0LnXkwWIq/G+FMXzTrnWIrtEcRhitc8MLow3KbFOSZ0uul/3Ks 1Ls5c97AVajh35wNYblkSqt0rJEf4iDa0HX8COpxV4wKpRG8Ej3b3OQ0z1F+G8iBHWs/ D4zNCAVx5fWQEYfO7VLepGRoD1qdlhbCKu2vQYD2yloBgp9rlYWcYOXmHwNz4tM6IhLe IAPQ== X-Gm-Message-State: APjAAAVQ8FTm5K70D25HrfpztFu5Qzb5dAsHZZm11pfLMTfPL6DM/cNz ulTwCtUnL42apxI0WPC7Xtijsw== X-Google-Smtp-Source: APXvYqwj99ewljN/2eNEtZwxUEhpvSSsx4bNvgHZ0BHqZ40FJVAPbsv9N4Vg1chNfOmR+rCc2WYSLg== X-Received: by 2002:adf:fd41:: with SMTP id h1mr6591594wrs.155.1553694682432; Wed, 27 Mar 2019 06:51:22 -0700 (PDT) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id b134sm66288wmd.26.2019.03.27.06.51.18 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Wed, 27 Mar 2019 06:51:18 -0700 (PDT) Date: Wed, 27 Mar 2019 14:51:16 +0100 From: Tomas Vondra To: "Fred .Flintstone" Cc: Mark Kirkwood , Tom Lane , Michael Paquier , Andreas Karlsson , Chris Travers , Tatsuo Ishii , Alvaro Herrera , Euler Taveira , Julien Rouhaud , Postgres hackers Subject: Re: PostgreSQL pollutes the file system Message-ID: <20190327135116.GA17983@development> References: <754d8607-682e-6f59-6870-faee5fa0820c@2ndquadrant.com> <20190321.084132.2186284141219540889.t-ishii@sraoss.co.jp> <20190321004919.GE20192@paquier.xyz> <10036.1553176960@sss.pgh.pa.us> <20190322003611.GK20192@paquier.xyz> <31754.1553220346@sss.pgh.pa.us> <3edd2644-eaf2-41e0-aa7a-92786d25b29c@catalyst.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.3 (2019-02-01) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Mar 27, 2019 at 02:31:14PM +0100, Fred .Flintstone wrote: >Many of these are gone in the modern PostgreSQL, a few remain. >https://packages.ubuntu.com/disco/amd64/postgresql-client-11/filelist > >/usr/lib/postgresql/11/bin/clusterdb >/usr/lib/postgresql/11/bin/createdb >/usr/lib/postgresql/11/bin/createuser >/usr/lib/postgresql/11/bin/dropdb >/usr/lib/postgresql/11/bin/dropuser >/usr/lib/postgresql/11/bin/pg_basebackup >/usr/lib/postgresql/11/bin/pg_dump >/usr/lib/postgresql/11/bin/pg_dumpall >/usr/lib/postgresql/11/bin/pg_isready >/usr/lib/postgresql/11/bin/pg_receivewal >/usr/lib/postgresql/11/bin/pg_recvlogical >/usr/lib/postgresql/11/bin/pg_restore >/usr/lib/postgresql/11/bin/psql >/usr/lib/postgresql/11/bin/reindexdb >/usr/lib/postgresql/11/bin/vacuumdb > >Can we rename clusterdb, reindexdb and vacuumdb to carry the pg_ prefix? > I think the consensus in this thread (and the previous ancient ones) is that it's not worth it. It's one thing to introduce new commands with the pg_ prefix, and it's a completely different thing to rename existing ones. That has inherent costs, and as Tom pointed out the burden would fall on people using PostgreSQL (and that's rather undesirable). I personally don't see why having commands without pg_ prefix would be an issue. Especially when placed in a separate directory, which eliminates the possibility of conflict with other commands. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services