From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
---|---|
To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [patch] pg_ctl init extension |
Date: | 2009-09-18 06:51:56 |
Message-ID: | 1253256716.1242.56.camel@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bernd Helmle píše v čt 17. 09. 2009 v 23:26 +0200:
>
> --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.
hmm, I could modify it that all args after init keyword will be pass to
the initdb like this:
pg_ctl -D /tmp/db init [<my favorite switches>]
initdb [<my favorite switches>]
and "pg_ctl -h init" will show help which commands are allowed.
Zdenek
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-09-18 06:53:24 | Re: Hot Standby 0.2.1 |
Previous Message | Albe Laurenz | 2009-09-18 06:50:35 | Re: Feedback on getting rid of VACUUM FULL |