Voting: "pg_ctl init" versus "initdb"

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: pgsql-general(at)postgresql(dot)org
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Voting: "pg_ctl init" versus "initdb"
Date: 2009-11-14 14:07:45
Message-ID: 1258207665.1456.21.camel@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,

I prepared patch which extend pg_ctl functionality and add "init"
command which do same thing like initdb (it calls initdb on the
background). The idea behind this is to have only one command which
control database. pg_ctl already has "start", "stop", "restart",
"reload" and so on. To have "init" is logical. There is also second
reason for that. Initdb does not fit pg binaries naming convection which
could lead to name conflict in the /usr/bin.

Because there is doubt if someone else want this I would like to ask
here for your opinion. There are following options:

1) Yeah I like pg_ctl init

"pg_ctl init" will be preferred method and initdb will
disappear from usr/bin in the future.

2) Good, but keep initdb as well

pg_ctl init and initdb stays forever

3) Do not touch my lovely initdb

pg_ctl init is nonsense, initdb is only correct way.

Thanks for your response

Zdenek

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Sabino Mullane 2009-11-14 15:28:55 Re: Upgrading databases
Previous Message Martin Gainty 2009-11-14 13:12:31 Re: Rejected token 3A37-A32F-9E8B