From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Joe Conway <mail(at)joeconway(dot)com>, pgsqlrpms-hackers(at)pgfoundry(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM init |
Date: | 2006-08-26 23:01:55 |
Message-ID: | 20060826230155.GM73562@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Aug 26, 2006 at 01:32:17PM -0700, Joshua D. Drake wrote:
> Jim C. Nasby wrote:
> >On Fri, Aug 25, 2006 at 07:21:50AM -0700, Joe Conway wrote:
> >>We also decided to turn off the init script execution entirely. The DBAs
> >>were more comfortable with a manual database startup for a production
> >>machine anyway (this is the way they typically handle Oracle databases
> >>also). They get paged if the server ever goes down unplanned, and in
> >>that event they like to check things out before bringing the db back up.
> >>For planned outages, database startup is simply part of the plan.
> >
> >I'd *really* like to have an official way to just disable the initdb
> >code entirely.
>
> I am not exactly sure why we initdb at all. IMHO it would be better if
> the start script just checked if there was a cluster. If not, it
> wouldn't start, it would error with: You do not have a cluster, please
> read man page on initdb.
As Tom mentioned, it's for newbie-friendliness. While I can understand
that, I think it needs to be easy to shut that off.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-08-26 23:16:52 | Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM init |
Previous Message | Jim C. Nasby | 2006-08-26 22:59:03 | Re: integration of pgcluster into postgresql |