From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: initdb should create a warning message [was Re: |
Date: | 2003-12-01 16:39:02 |
Message-ID: | 3FCB6EA6.2060908@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-docs pgsql-hackers |
Greg Stark wrote:
>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.
>>
>>
>
>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.
>
>
>
Renaming the directories is the only suggestion I've seen that makes
sense. The others remind me of the warning that is now placed on coffee
cup lids at fast food places: "Caution, Contents May Be Hot".
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2003-12-01 17:26:35 | Re: initdb should create a warning message [was Re: |
Previous Message | Ian Harding | 2003-12-01 16:25:25 | Re: Misplaced modifier in Postgresql license |
From | Date | Subject | |
---|---|---|---|
Next Message | Halley Pacheco de Oliveira | 2003-12-01 17:01:49 | PostgreSQL 7.4 Documentation - create_trigger.sgml |
Previous Message | Greg Stark | 2003-12-01 16:16:56 | Re: initdb should create a warning message [was Re: |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2003-12-01 16:45:57 | Re: Max number of rows in a table |
Previous Message | Tom Lane | 2003-12-01 16:35:38 | Re: Max number of rows in a table |