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 1hEw6Z-0000p1-7z for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Apr 2019 13:20: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 1hEw6W-0003Fb-JQ for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Apr 2019 13:20:28 +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 1hEw6W-00034f-8Z for pgsql-hackers@lists.postgresql.org; Fri, 12 Apr 2019 13:20:28 +0000 Received: from mail-qt1-x843.google.com ([2607:f8b0:4864:20::843]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hEw6O-0004kD-7Z for pgsql-hackers@lists.postgresql.org; Fri, 12 Apr 2019 13:20:26 +0000 Received: by mail-qt1-x843.google.com with SMTP id s15so11155861qtn.3 for ; Fri, 12 Apr 2019 06:20:19 -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:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=2uyGm34skQ4sX2jSrD9RTShc5oGAp87yBf3G36aycec=; b=dDLY2rNi3tLQjqLrcciuuxp85TM1+3/0QOB2XTC3KoTSFtiGUo0wBqx2voRSA8TxeF 8iAvmpQwerWYM5nxgsXySzu1jm9i5h/5k2KFVQE6fUA5rvvBKX/dZgt4lqYgAxqtrMI2 +TonrtP7xeRoRSc1lu9B/wNrB/GyXehx2LxOtENCw6wi0xebupjqQ3VDk3fhndOHOJo+ XPrNxxa9A/zfZTpKxFo05h23bJliEYRa5T4eIP8raYb+RUsTQySYKIXNll9C/vOlwnoq cfKUpMyLSbgN6koYMLaoyDmZu8MMZe64tHxOtQIJV/mUiTOlXcG9EYOgir7GWzEXKC+c RSKA== 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:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=2uyGm34skQ4sX2jSrD9RTShc5oGAp87yBf3G36aycec=; b=NGCxdRlKWvnPGaCMVyBoKvnBI6lqUKCHr+vhGUI1WcGVZhey7OUPo25aT0vueD9YCe HM/gFoJ0G3d/vUycpmTjQeIjiPg/eZSVodIH9DK0MnzSSZqIWVMP9HtRFz7i5cZan+EG Ll2xGh70YCKe/+by2b2SX3Qvd0WMR4XPzZeuyv7v85x6vjQFbi3dFpD45RESK3tdWgZE Y0xWQqyOw2zwFICnBm5DQMCqJsqFObb9YDhcsygMaO4IuJn6mdGRHTp7kvF+y1X+sPtN 4voz2S5Kl0If/EvUDSfN1P2Q70amy77fuYuqdidiuch0cBg2v3YLYW1EpBHJ2U/0sMzH cung== X-Gm-Message-State: APjAAAWvqFJpNCHnl8T23o64VzGH4DE2KJU+fcqeamyamdlLxDAxsXhW mk4jA8LY0b/gNVw6J3cn6yAo+g== X-Google-Smtp-Source: APXvYqwQzZZI6fu3OZiAa4/ZoIdSafwQRIlJiqJJPbhPDt3lUHbF0kMLZTrD3WykYu4q0LdC3lAEgg== X-Received: by 2002:ac8:f86:: with SMTP id b6mr46867130qtk.330.1555075218245; Fri, 12 Apr 2019 06:20:18 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id s12sm24617044qke.36.2019.04.12.06.20.17 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 12 Apr 2019 06:20:17 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id A84EB12101A; Fri, 12 Apr 2019 09:20:14 -0400 (-04) Date: Fri, 12 Apr 2019 09:20:14 -0400 From: Alvaro Herrera To: Daniel Gustafsson Cc: "Fred .Flintstone" , Peter Eisentraut , Tatsuo Ishii , Joe Conway , Pavel Stehule , Christoph Berg , Tom Lane , Andres Freund , Andreas Karlsson , Tomas Vondra , Mark Kirkwood , Michael Paquier , Chris Travers , Euler Taveira , Julien Rouhaud , Postgres hackers Subject: Re: PostgreSQL pollutes the file system Message-ID: <20190412132014.GA6802@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7JPwZOAHfqebBcy9dxAT1zbZ3miMHfUItBVTWx6N4pHPlRgYx0-IO9tthHBRlFKVhKybS8H8ArMHr0AJEF_NfVQHnftQE3fsUgNcegY-Pes=@yesql.se> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Apr-12, Daniel Gustafsson wrote: > There are many good reasons for the changes proposed in this thread, but I'm > not sure if discoverability is one. Relying on autocompleting a filename to > figure out existing tooling for database maintenance and DBA type operations > seems like a fragile usecase. > > If commandline discoverability is of importance, providing a summary of the > tools in "man postgresql" seems like a better option. The first comment in the LWN article: "It's broken and obviously a bad idea but we've been doing it for so long we shouldn't attempt to fix it" IMO the future is longer than the past, and has more users, so let's do it right instead of perpetuating the mistakes. ... unless you think PostgreSQL is going to become irrelevant before 2050. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services