Content-Type: text/plain;
  charset="iso-8859-1"
From: Tilo Schwarz <mail@tilo-schwarz.de>
To: pgsql-hackers@postgresql.org
Subject: Re: initdb should create a warning message [was Re:
Date: Mon, 1 Dec 2003 18:56:46 +0100
User-Agent: KMail/1.4.3
References: <20031126043752.51857.qmail@web10804.mail.yahoo.com>
	<1070263797.7719.2662.camel@linda.lfix.co.uk>
	<873cc4ecnb.fsf@stark.dyndns.tv>
In-Reply-To: <873cc4ecnb.fsf@stark.dyndns.tv>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200312011856.46117.mail@tilo-schwarz.de>

Greg Stark writes:
> Oliver Elphick <olly@lfix.co.uk> writes:
> > Then it needs to be stated very prominently.  But the place to put a
> > sign saying "Dangerous cliff edge" is beside the path that leads along
> > it.Greg Stark <gsstark@mit.edu>, p
>
> The only way to make this prominent would be a file with the *name* "THIS
> DIRECTORY CONTAINS CRITICAL DATA". Not a "README" with that message insid=
e.

That's exacly what I did, after some "root" came along and moved my pgdata=
=20
away while postmaster was running. The data was not that important in that=
=20
case, but nevertheless I put a file with a name like

NEVER_MOVE_THIS_DIRECTORY_WHILE_POSTMASTER_PROCESS_IS_RUNNING.txt

in pgdata and wrote a few lines in that file, how to shutdown postmaster=20
properly.

But renaming pgdata to something like that would be even better and could b=
e=20
done alrealy (if I'm right).

Regards,
=09
	Tilo