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 1h9Cu8-0000QH-Hb for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 18:04:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h9Cu6-0003UO-1x for pgsql-hackers@arkaria.postgresql.org; Wed, 27 Mar 2019 18:03:58 +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 1h9Cu5-0003UH-MP for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 18:03:57 +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 1h9Cty-0007Pm-R8 for pgsql-hackers@lists.postgresql.org; Wed, 27 Mar 2019 18:03:56 +0000 Received: by mail-qt1-x841.google.com with SMTP id s15so4280509qtn.3 for ; Wed, 27 Mar 2019 11:03:50 -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=i+reHZMTCC1y2sIQAVToaHKhXl3cZumIb1Ed0oSrW6E=; b=tid5an7zQIClrM6gkvsJLEVE5HUMwK8fC9u5YTscRgE6vyRa9vAWHPOow7hKFzlULh NZCxm/O8lGtaEAFCGzBmPHe2pT/ChcizlcEzKIljUCG482lR7GlFaBKGSRBI68eQlR1Y 92BTmjUDwycK+9SEwhmGFfkPbNx9+rxJZLVuGWpLISW05IDKHuH2GscK9SZA0lQ2iyJI yv0wmbbB6QLAFt2kllbRh0cltR8UQnEugIwjpNfYeYbFglMv4iOLjiDvTDh6+hA6FGbh A6t5+/0o7kAmNuCQ1lwghReNvGiI+s7J1wMGV0+NJ87piuk1mxFVQJMiexMcQe3TVwAi zbDA== 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=i+reHZMTCC1y2sIQAVToaHKhXl3cZumIb1Ed0oSrW6E=; b=XwrJdIOcOxLzoV5kAZ/rHFMZYvjSxWukP3l7c9y5j1hfvGWwPsbH5U9NPLv6konmnw mEljf1d6yPWmY1aZmOYOTKF9iA5bNachb/g4uDTgpbboeysB1P7tXB5JcTeEHcKUXHLi NnxUTxinCNTOhe6zSsZ42fvvwCV00uKL5CiJ3wdBQ5v1bRzmqNKFCeZrvOk2+ylZJioP uit6jcmDG4sUjOrEufIgbwe+TW54PUmzvdge7q3MCJHOLGe3nDoTX43httSbVEaG/hxI Sc4pi9xtYCFSScbxYiGRDUKdiwIUIAAwiL/uzOKVv9BVHscdneuUrPZ3V+PcodiU02K9 YDYw== X-Gm-Message-State: APjAAAWLcn8bh2131Y2gjVUK7GHY+DFv7mhenX1d6iE5x64kwSvKF0ip o+CNz8BAXC9z8oBygTXwPLARKw== X-Google-Smtp-Source: APXvYqwdgnvlbYd1X7wb25c/sjRMmrcEEPA9xvGwvZJQVGW3xqUqmOP2JxISjQME6gCqzsY55dfwGA== X-Received: by 2002:aed:3faa:: with SMTP id s39mr26794476qth.280.1553709829724; Wed, 27 Mar 2019 11:03:49 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([201.186.80.67]) by smtp.gmail.com with ESMTPSA id 65sm11435519qkm.61.2019.03.27.11.03.48 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 27 Mar 2019 11:03:49 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 73893120416; Wed, 27 Mar 2019 15:03:47 -0300 (-03) Date: Wed, 27 Mar 2019 15:03:47 -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: <20190327180347.GA31173@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <32073.1553706587@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: > > 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. > > Nobody is defending the existing names as being something we'd pick > if we were picking them today. The question is whether changing them > is worth the pain. (And, one more time, may I point out that most > of the pain will be borne by people not on this mailing list, hence > unable to vote here.) I don't think there is any reasonable argument > that said pain will be justified for any of them except maybe createuser > and dropuser. The implicit argument here is that existing users are a larger population than future users. I, for one, don't believe that. I think taking no action is a disservice to future users. Also, that modifying the code will be utterly painful and that less administrative code will be written in the future than has already been written. We *could* run a poll on twitter/slack/website to get a feeling on a wider population. That would still reach mostly existing Postgres users, but at least it would be much more diverse than this group. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services