From: | Tilo Schwarz <mail(at)tilo-schwarz(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: initdb should create a warning message [was Re: |
Date: | 2003-12-01 17:56:46 |
Message-ID: | 200312011856.46117.mail@tilo-schwarz.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-docs pgsql-hackers |
Greg Stark writes:
> Oliver Elphick <olly(at)lfix(dot)co(dot)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(at)mit(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2003-12-01 19:34:46 | Re: eRserver |
Previous Message | Oliver Elphick | 2003-12-01 17:26:35 | Re: initdb should create a warning message [was Re: |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-12-01 17:59:20 | Re: PostgreSQL 7.4 Documentation - create_trigger.sgml |
Previous Message | Oliver Elphick | 2003-12-01 17:26:35 | Re: initdb should create a warning message [was Re: |
From | Date | Subject | |
---|---|---|---|
Next Message | Manfred Koizar | 2003-12-01 18:17:10 | Re: [HACKERS] Index creation takes for ever |
Previous Message | Tom Lane | 2003-12-01 17:41:04 | Re: Max number of rows in a table |