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 1h6mZL-0007cu-DM for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Mar 2019 01:32:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6mZK-0001rd-64 for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Mar 2019 01:32:30 +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 1h6mZJ-0001oY-Tm for pgsql-hackers@lists.postgresql.org; Thu, 21 Mar 2019 01:32:29 +0000 Received: from mail-wr1-x444.google.com ([2a00:1450:4864:20::444]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6mZH-0008DH-Bq for pgsql-hackers@lists.postgresql.org; Thu, 21 Mar 2019 01:32:29 +0000 Received: by mail-wr1-x444.google.com with SMTP id w1so4853932wrp.2 for ; Wed, 20 Mar 2019 18:32:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Mz4Msq/53eqSB4cTvFsnO6aXPPsKr7VU7k5c3TgYOxQ=; b=GyYjANr9QkYnJDrrGJkH5csaZBaTRnESCPAf2woSkwfO1omQZVEo3HDX6iBhbo+u4S zIjAcZE/YIzro1XZgCK/s9VNrnaTu4uC/lE+yhzlNIzFYwG5gvTz98yQtfRJnrAv4uJV EYZDKGNxlolaOn8FduYe2dcX1qGZWZhlYMmifUDMZD21U++iLaTf1KkgWp/uvdl8Dyo/ a1VBrqL3wDGnwxPdKfo1BBNKkQgNM3/+RRUuHdHn3F8P43rWLiC5RwGMRcSqoC95U3iu FazLomLg6zrUb/qdct1BvkGxyi77/RwRP8Sn/z2CixAxqM44pWLOvaW64kSJtlWcDG8u bDaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Mz4Msq/53eqSB4cTvFsnO6aXPPsKr7VU7k5c3TgYOxQ=; b=jmbPfB/yZjnO2Clxd5hKcKgDaDyHmEPcUdJ4yqZ8h2aUEZR/NNW5ZajqMSjcK3qvoz cxRulGXeCJsVDvguZdJr3yTOyzttutzmzABE0sVSE+6gW9ZrmNFRDl0QzEdK7FUVSvsE BEOOPEdyQME6zBPENvbx5Lwac+5Jksahykily9LhvZanql5RyvKejjPymN8GX8mk8Wc0 Ydtczv3ZYVtjchC/q9cDnUJzDYplYU0F6LL/OXAeSYai0iv6SWc8I6QXP4EwtVW9eRTY Ae9MnuEJwN15DN62ZToeydEl/WXF/+Xb1H9yv0a1O0DrpRqc88uJ87S4VXEbpqs+/SOH DzOg== X-Gm-Message-State: APjAAAUm2TDZ70isOComQ54AX+2Uyw0iO54xw6egX8Tbrli1wT7bK2Xo ezogZD1l8wTwUa1CGTSDynyhBDUsNLcr/OroKAE0l/KzbQi9MSv1nCDNHsKEVz2rdvAoa5bickq ODG8FSOz59dMb4HlGDCNj2jGjTqINnhUpanNxkFbGVo561LQGGva1m7OxNstnBL+g/tm3H0fvvB 9+iaJJcDHux0ifUoAI612rCw== X-Google-Smtp-Source: APXvYqy9RhJjAfXgJMVhQgzciXIkVrjExmCpVAobS2UqaphgtgZCIAhdF2jtIG4hyLHoA2AK0qT1JA== X-Received: by 2002:a5d:4907:: with SMTP id x7mr702828wrq.133.1553131945186; Wed, 20 Mar 2019 18:32:25 -0700 (PDT) Received: from [10.137.0.17] (ip-86-49-243-43.net.upcbroadband.cz. [86.49.243.43]) by smtp.gmail.com with ESMTPSA id x22sm4969249wmc.19.2019.03.20.18.32.23 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Wed, 20 Mar 2019 18:32:24 -0700 (PDT) Subject: Re: PostgreSQL pollutes the file system To: Michael Paquier , Tatsuo Ishii Cc: alvherre@2ndquadrant.com, euler@timbira.com.br, tgl@sss.pgh.pa.us, rjuju123@gmail.com, chris.travers@adjust.com, andreas@proxel.se, eldmannen@gmail.com, pgsql-hackers@lists.postgresql.org References: <20190320180832.GA11614@alvherre.pgsql> <754d8607-682e-6f59-6870-faee5fa0820c@2ndquadrant.com> <20190321.084132.2186284141219540889.t-ishii@sraoss.co.jp> <20190321004919.GE20192@paquier.xyz> From: Tomas Vondra Message-ID: <2b6890db-acca-8f44-de4f-f43d70d57000@2ndquadrant.com> Date: Thu, 21 Mar 2019 02:32:23 +0100 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: <20190321004919.GE20192@paquier.xyz> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 3/21/19 1:49 AM, Michael Paquier wrote: > On Thu, Mar 21, 2019 at 08:41:32AM +0900, Tatsuo Ishii wrote: >>> Can someone describe a scenario where this (name of the binary not >>> clearly indicating it's related postgres) causes issues in practice? On >>> my system, there are ~1400 binaries in /usr/bin, and for the vast >>> majority of them it's rather unclear where do they come from. > > Naming conflict because our binary names are too generic? createdb > could for example be applied to any database, and not only Postgres. > (I have 1600 entries in /usr/bin on a Debian installation.) > Maybe. Do we actually know about such cases? Also, isn't setting --prefix a suitable solution? I mean, it's what we/packagers do to support installing multiple Pg versions (in which case it'll conflict no matter how we rename stuff) anyway. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services