From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(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:16:52 |
Message-ID: | 44F0D664.30500@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
>
Well, in the case of RPMS built with the pgfoundry pgsqlrpms project
init script, it looks to me like it is already disabled: see
http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsqlrpms/patches/8.2/postgresql.init?rev=1.2&content-type=text/x-cvsweb-markup
In the case of Redhat/Fedora supplied RPMs, presumably it is not
disabled as a matter of policy, the idea being to make starting postgres
as easy as possible. What you could do is to ask them to add some code
to honor the setting of a variable called say, PG_INITDB, which you
would set in the appropriate place in /etc/sysconfig.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2006-08-26 23:27:43 | Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM init |
Previous Message | Jim C. Nasby | 2006-08-26 23:01:55 | Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM init |