Re: initdb should create a warning message [was Re: - Mailing list pgsql-hackers

From Tilo Schwarz
Subject Re: initdb should create a warning message [was Re:
Date
Msg-id 200312011856.46117.mail@tilo-schwarz.de
Whole thread Raw
In response to Re: initdb should create a warning message [was Re:  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
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 inside.

That's exacly what I did, after some "root" came along and moved my pgdata
away while postmaster was running. The data was not that important in that
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
properly.

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

Regards,Tilo


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Max number of rows in a table
Next
From: Manfred Koizar
Date:
Subject: Re: [PATCHES] Index creation takes for ever