Skip site navigation (1) Skip section navigation (2)

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

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
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 20:32:17
Message-ID: 44F0AFD1.1070306@commandprompt.com (view raw or flat)
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.

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.

Joshua D. Drake


-- 

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/



In response to

Responses

pgsql-hackers by date

Next:From: HayesDate: 2006-08-26 20:36:55
Subject: Re: An Idea for planner hints
Previous:From: Joshua D. DrakeDate: 2006-08-26 20:31:08
Subject: Re: [HACKERS] New XML section for documentation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group