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 1h99Sk-0006WW-Sj for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 14:23: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 1h99Sj-0007Ft-DW for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 14:23:29 +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 1h99Sj-0007Fg-5E for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 14:23:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h99Sg-0000NE-5s for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 14:23:27 +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 x2REN63F017472; Wed, 27 Mar 2019 10:23:06 -0400 From: Tom Lane To: Alvaro Herrera cc: Tomas Vondra , "Fred .Flintstone" , Mark Kirkwood , Michael Paquier , Andreas Karlsson , Chris Travers , Tatsuo Ishii , Euler Taveira , Julien Rouhaud , Postgres hackers Subject: Re: PostgreSQL pollutes the file system In-reply-to: <20190327140018.GA15038@alvherre.pgsql> References: <20190327140018.GA15038@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Wed, 27 Mar 2019 11:00:18 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17470.1553696586.1@sss.pgh.pa.us> Date: Wed, 27 Mar 2019 10:23:06 -0400 Message-ID: <17471.1553696586@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > On 2019-Mar-27, Tomas Vondra wrote: >> 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 thought the consensus was to rename them, and install symlinks to the > old names. The question is what's the endgame. We haven't actually fixed the complained-of confusion problem unless we eventually remove createuser and dropuser under those names. Are we prepared to force script breakage of that sort, even over a multi-year deprecation cycle? (As a comparison point, I note that we still haven't removed the "postmaster" symlink, though it's been deprecated for at least a dozen years.) regards, tom lane