From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Fred .Flintstone <eldmannen@gmail.com>
Cc: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Andreas Karlsson <andreas@proxel.se>
Cc: Chris Travers <chris.travers@adjust.com>
Cc: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: Euler Taveira <euler@timbira.com.br>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: PostgreSQL pollutes the file system
Date: Wed, 27 Mar 2019 15:03:47 -0300
Message-ID: <20190327180347.GA31173@alvherre.pgsql> (raw)
In-Reply-To: <32073.1553706587@sss.pgh.pa.us>
On 2019-Mar-27, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-pkg-debian@postgresql.org
Cc: alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, tomas.vondra@2ndquadrant.com, eldmannen@gmail.com, mark.kirkwood@catalyst.net.nz, michael@paquier.xyz, andreas@proxel.se, chris.travers@adjust.com, ishii@sraoss.co.jp, euler@timbira.com.br, rjuju123@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: PostgreSQL pollutes the file system
In-Reply-To: <20190327180347.GA31173@alvherre.pgsql>
References: <32073.1553706587@sss.pgh.pa.us> <20190327180347.GA31173@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox