Re: [HACKERS] Removing binaries (was: createlang/droplang deprecated) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Removing binaries (was: createlang/droplang deprecated)
Date
Msg-id CA+TgmoZcmmYxJjfScOzO=8vOC6579=bW995hOQCCfrvmNUw60Q@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Removing binaries (was: createlang/droplang deprecated)  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [HACKERS] Removing binaries (was: createlang/droplang deprecated)  (Jan de Visser <jan@de-visser.net>)
List pgsql-hackers
On Sat, Mar 18, 2017 at 4:12 PM, Magnus Hagander <magnus@hagander.net> wrote:
> createdb, dropdb - also not clear they're about postgres, more likely to be
> used by mistake but not that bad. That said, do they add any *value* beyond
> what you can do with psql -c "CREATE DATABASE"? I don't really see one, so
> I'd suggest dropping these too.

That would annoy me, because I use these constantly.  I also think
that they solve a problem for users, which is this:

[rhaas ~]$ psql
psql: FATAL:  database "rhaas" does not exist
[rhaas ~]$ psql -c 'create database rhaas;'
psql: FATAL:  database "rhaas" does not exist
[rhaas ~]$ gosh, i know i need to connect to a database in order to
create the database to which psql tries to connect by default, so
there must be an existing database with some name, but what exactly is
that name, anyway?
-bash: gosh,: command not found

There was an occasion when this exact problem almost caused me to give
up on using PostgreSQL.  Everybody here presumably knows that
template1 and postgres are the magic words you can add to the end of
that command line to make it work, but that is NOT self-evident to
newcomers.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] logical replication access control patches
Next
From: Jan de Visser
Date:
Subject: Re: [HACKERS] Removing binaries (was: createlang/droplang deprecated)