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 1h99uw-00081M-8i for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 14:52:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h99uu-0006SE-FY for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 14:52:36 +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 1h99uu-0006S6-3L for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 14:52:36 +0000 Received: from mail-qt1-x841.google.com ([2607:f8b0:4864:20::841]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h99ur-00032a-DZ for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 14:52:34 +0000 Received: by mail-qt1-x841.google.com with SMTP id t28so19146215qte.6 for ; Wed, 27 Mar 2019 07:52:33 -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=lTqvJuirOAlvzkqczIpiQUqoCSwV0kVWqsmDyHZYzTo=; b=y3FwCs5oeB0ILQ0NCi6/kQj2jlfCb7jiXot6D/jZpKkzUlcjaHVtaFtp2aIaEqdWRt Vkp/ozbKpG+tC1Ve5ASrb0h98/VB4AhgWWL4S/aTJb6fW12Yf1Hpoumv/WykpVpBwE4g ifdvbpp5GlMKc+X2HbUs6f5d9WUtBddcJli0CU03J2EShLwVUIDqaZ3L8J1x+yWdxrAb xS2a89c+pVRYAM6u2ScBznIuyo/+KrXF0OLJQ7IYkS6WgKDWos9jyBsN941lnkYLdpw4 KX0c1Rj2LeVgRzNaXWw4rYXp6tqy8V/Y0ay4IV1xPPEzkGpOgOQzkOa6PupZwhitENZx uHJQ== 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=lTqvJuirOAlvzkqczIpiQUqoCSwV0kVWqsmDyHZYzTo=; b=Zn13JEMcB9a0ExI/06AS+oEwH+/YobuvcDA7SkzICHEePiVpbziMMl01CROl6PUQVe P7Si94BLflqSBbqwJdaUVKQ93Gn2aISxhVOkJvOtM62CzUmcxyoEnsEMY/vjaYzR0Bf7 PgfQ5SIUqCaP78kU125M/6COyJ+da48uPv5mwrVzqD3OkFFbUTGj3AOmvgBQJroKIsOl ktHqrz+f5/yGZbQtov7ETy5VKyUotxj531SgeuoH3TESGb2becharZNviqiXWfktGpCs GYQcNHD3g4AyL3cnfA9+nnTxkRX0rBhqjjssWUk6f4Up5SNjbqqOyFeFGSXbgiLydGa6 HQrA== X-Gm-Message-State: APjAAAVmBTRtxb/Utcoh2xaVXy8QAG0z969RUISFIBp/znICchlCEmnf PKajfrtUwryMWoRzWqeKrQ0PbQ== X-Google-Smtp-Source: APXvYqxATtwTu8vBjIUYSoiQdODQW0YNCC204lf0gIEdSIl3bUFViRN85wzHBOFQMSlLppUCTLiNVA== X-Received: by 2002:a0c:9924:: with SMTP id h33mr32079293qvd.156.1553698352581; Wed, 27 Mar 2019 07:52:32 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id x8sm859969qtj.45.2019.03.27.07.52.31 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 27 Mar 2019 07:52:32 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 05153120BB3; Wed, 27 Mar 2019 11:52:30 -0300 (-03) Date: Wed, 27 Mar 2019 11:52:29 -0300 From: Alvaro Herrera To: Tom Lane 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 Message-ID: <20190327145229.GA19492@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <17471.1553696586@sss.pgh.pa.us> 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-Mar-27, Tom Lane wrote: > 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. Well, partly we have, because there mere act of having a symlink documents the command via the symlink target. Somebody proposed to rename createuser not to pg_createuser, though, but rather to pg_createrole; ditto dropuser. That seems to make sense. I additionally proposed (nobody replied to this part) that we could have the command print a WARNING if the argv[0] is shown to be the old name. Not necessarily in pg12; maybe we can have them print such a warning in pg13, and then remove the old names three years from now, or something like that. I suppose that if you're a Postgres developer, you naturally expect that "createdb" creates a Postgres DB. What if you use multiple database systems, and then only occasionally have to do DBA tasks? I find this POV that createdb doesn't need renaming a bit self-centered. > Are we prepared to force script breakage of that sort, even over a > multi-year deprecation cycle? Why not? > (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.) I don't think that change was because of executable namespace pollution or user confusion. (Commit 5266f221a2e1, can't find the discussion though.) -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services