Re: [patch] pg_ctl init extension

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>, Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [patch] pg_ctl init extension
Date: 2009-09-17 21:26:14
Message-ID: 23E60DABA5335CA0D1E7EE5A@amenophis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On 17. September 2009 23:00:12 +0300 Peter Eisentraut <peter_e(at)gmx(dot)net>
wrote:

> f the name is a problem, why not change the name? What you are
> proposing above is effectively a very elaborate name change, so why not
> go for a simpler one?

I don't like the solution by using -o "<initdb options>" to push down
command line options to initdb. I always had the opinion that this was (and
is) a valid workaround for postgres itself, but it doesn't feel correct to
expose that further to initdb and its purposes.

My 2 cents...

--
Thanks

Bernd

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-09-17 21:28:16 Re: [COMMITTERS] pgsql: CVS NULL Documentation Clearify documentation of CVS's output of
Previous Message Tom Lane 2009-09-17 21:22:17 Re: [COMMITTERS] pgsql: CVS NULL Documentation Clearify documentation of CVS's output of