From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Donn Washburn <n5xwb(at)comcast(dot)net> |
Cc: | PostgreSQL Novice elist <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Getting started |
Date: | 2010-03-26 19:29:20 |
Message-ID: | 19112.1269631760@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Donn Washburn <n5xwb(at)comcast(dot)net> writes:
> After looking at /etc/init.d/postgresql there is no mention to initdb
> other than under start) /usr/bin/initdb. The script is a openSuSE
> script that only has things like start), stop) and status) which are
> recognized.
Mph. So what you've got is one of the ones that automatically fires off
initdb if it doesn't see something that looks like a Postgres data
directory in the right place at "start" time. This is nice in that
it saves one step for newbies, but I think most distros are migrating
to a separate "initdb" action for that. There have been a couple of
well-publicized catastrophes wherein somebody's database got trashed by
a start script mistakenly firing up initdb, so people are now taking the
view that auto-initdb is more risk than it's worth. I'd counsel against
using an auto-initdb start script if you have the database on any sort
of external storage (particularly NFS/SAN), but if it's on the same
drive as the OS then it's probably safe enough. Just FYI.
> It is not the one that likely comes with postgres.
There isn't really a "standard" init script for Postgres; every distro
rolls their own.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mladen Gogala | 2010-03-26 19:39:13 | Re: Getting started |
Previous Message | Donn Washburn | 2010-03-26 18:59:16 | Re: Getting started |