Re: initdb profiles

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of
> Andrew - Supernews
> Sent: 09 September 2005 08:16
> To: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] initdb profiles
>
> On 2005-09-08, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > Andrew - Supernews wrote:
> >> On 2005-09-08, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> >> > Andrew - Supernews wrote:
> >> >> Running initdb behind the scenes is a proven dangerous practice
> >> >
> >> > Please elaborate.
> >>
> >> Example instance:
> >> http://archives.postgresql.org/pgsql-hackers/2004-12/msg00851.php
> >
> > If you run your database on NFS, your warranty is void.
>
> NFS has nothing to do with it.

Well, it sorta did in that case, but I see where you're coming from.
What does have something to do with it is that iirc it was the rc.pgsql
script that ran initdb in the background at boot time when it didn't
find the data directory, so perhaps your statement would be more
accurate as:

"Automatically running initdb behind the scenes at system startup is a
proven dangerous practice"

We've distributed hundreds of thousands of copies of pgInstaller which
initdb's behind the scenes and never had any reported problems.

Regards, Dave