From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | <peter_e(at)gmx(dot)net>,<Zdenek(dot)Kotala(at)Sun(dot)COM> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [patch] pg_ctl init extension |
Date: | 2009-11-14 15:12:23 |
Message-ID: | 4AFE7477020000250002C87B@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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. We could filter this option out
in the script, but it seemed like you wanted to keep the script as
short and simple as possible....
-Kevin
From | Date | Subject | |
---|---|---|---|
Next 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" |
Previous Message | Kevin Grittner | 2009-11-14 14:33:00 | Re: tsearch parser inefficiency if text includes urls or emails - new version |