From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | peter_e(at)gmx(dot)net, Zdenek(dot)Kotala(at)Sun(dot)COM, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [patch] pg_ctl init extension |
Date: | 2009-11-14 16:25:53 |
Message-ID: | 14098.1258215953@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Peter Eisentraut wrote:
>> The patch is pretty straightforward,
>> but does anyone else actually want this? Comments?
> I agree that the initdb name seems odd next to the other executable
> names, but the functionality seems a little out of place to me in
> pg_ctl. The other options all correspond (more or less) to LSB init
> script actions (and we've been talking about the desirability of
> making that a closer fit); while this is something which would *not
> be appropriate* in an init script.
Well, it's not appropriate or safe as a default action, but there
already is a nonstandard "service postgresql init" action in at least
the PGDG and Red Hat init scripts. In fact, I believe that Zdenek's
entire rationale for this is predicated on the assumption that he can
eventually make initdb's disappearance transparent, if he can get
people used to using such a thing instead of initdb'ing by hand.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-11-14 16:26:50 | Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable" |
Previous Message | Magnus Hagander | 2009-11-14 15:41:00 | Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable" |