Re: Renaming some binaries

From: Andres Freund <andres(at)anarazel(dot)de>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Euler Taveira <euler(at)timbira(dot)com(dot)br>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Renaming some binaries
Date: 2016-08-26 20:03:41
Message-ID: 20160826200341.2hcl4bofy7kchphj@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016-08-26 22:01:58 +0200, Simon Riggs wrote:
> On 26 August 2016 at 18:26, Euler Taveira <euler(at)timbira(dot)com(dot)br> wrote:
>
> > I'm bringing this $subject into discussion again. Historically, we are
> > carrying binary names that have been confused newbies. createuser is the
> > worst name so for. Also, names like createdb, initdb, reindexdb, and
> > droplang does not suggest what product it is referring to. Adding a
> > prefix (pg_, pg, ...) would 'make things clear'. If we have a consensus
> > about this change, I suggest renaming the following binaries:
> >
> > clusterdb
> > createdb
> > createlang
> > createuser
> > dropdb
> > droplang
> > dropuser
> > initdb
> > oid2name
> > reindexdb
> > vacuumdb
> > vacuumlo
>
> Why not just remove them all and change the docs to suggest using
>
> psql -c "CREATE DATABASE foo"
> etc
>
> Less code, no confusion because we have just one client tool - psql.

Several of them have the ability to connect to several databases, some
even do that in parallel.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2016-08-26 20:09:59 Re: Renaming some binaries
Previous Message Joshua D. Drake 2016-08-26 20:02:55 Re: Renaming of pg_xlog and pg_clog