Search Postgresql Archives

Voting: "pg_ctl init" versus "initdb"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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




-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux