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

From: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: 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 02:08:19
Message-ID: 44F0FE93.6050400@zeut.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:
> Matthew T. O'Connor wrote:
>> Jim C. Nasby wrote:
>>> As Tom mentioned, it's for newbie-friendliness. While I can understand
>>> that, I think it needs to be easy to shut that off.
>>
>> I understand that, but it seems the whole problem of people
>> overwriting there data dir is because we initdb from the start
>> script. If we installed the datadir during the RPM install, it would
>> still be newbie friendly and would removed initdb from start script
>> solving that problem.
>
> initdb will not overwrite an existing installation.

Poorly chosen words. I meant, the problem where the start script will
create a new data dir when it doesn't see that one exists even though
one actually does exist it's just not available at the moment. Either
way, if the start scripts never created a data dir, then there is no
problem.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2006-08-27 02:24:29 Re: Adding fulldisjunctions to the contrib
Previous Message Jonah H. Harris 2006-08-27 02:07:57 Re: Adding fulldisjunctions to the contrib