Re: Safer auto-initdb for RPM init script

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsqlrpms-hackers(at)pgfoundry(dot)org>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Safer auto-initdb for RPM init script
Date: 2006-08-25 14:09:49
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA355BD@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I don't really want to remove the auto-initdb feature from the
> script, because it's important not to drive away newbies by making
> Postgres hard to start for the first time. But I think we'd better
> think about ways to make it more bulletproof.

Why does initdb have to happen on startup? Wouldn't it be much more
logical to do it at install time? (like we do in the win32 installer,
for example, I'm sure there are other examples as well)

//Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Böszörményi Zoltán 2006-08-25 14:18:42 Re: Performance testing of COPY (SELECT) TO
Previous Message Stefan Kaltenbrunner 2006-08-25 14:08:18 Re: Tricky bugs in concurrent index build