Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM init

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, 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-27 03:06:24
Message-ID: 44F10C30.4010308@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera 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.
>>
>
> This is trivial to do --- just add a /etc/<some_dir>/postgresql file
> that contains a line like
>
> AUTO_INITDB=0
>
> to turn the auto-initdb'ing feature of the init script off. If the file
> is not present or AUTO_INITDB is not defined to zero in that file, then
> the code behaves as today. I don't recall what the configuration
> directory is called in Redhat systems, but there is one in there (in
> Debian it's /etc/default).
>
>

I don't see anything like this in my FC5 box's init script.

Oh, and the place you put stuff like that on RH/FC systems is /etc/sysconfig

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2006-08-27 03:13:16 Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM init
Previous Message Andrew Dunstan 2006-08-27 03:02:04 Re: Adding fulldisjunctions to the contrib