Re: initdb should create a warning message [was Re:

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: initdb should create a warning message [was Re:
Date: 2003-12-01 16:16:56
Message-ID: 873cc4ecnb.fsf@stark.dyndns.tv
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-docs pgsql-hackers


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.

--
greg

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ian Harding 2003-12-01 16:25:25 Re: Misplaced modifier in Postgresql license
Previous Message Mike Mascari 2003-12-01 15:46:01 Re: [HACKERS] initdb should create a warning message [was Re: [ADMIN]

Browse pgsql-docs by date

  From Date Subject
Next Message Andrew Dunstan 2003-12-01 16:39:02 Re: initdb should create a warning message [was Re:
Previous Message Mike Mascari 2003-12-01 15:46:01 Re: [HACKERS] initdb should create a warning message [was Re: [ADMIN]

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2003-12-01 16:24:47 Re: Max number of rows in a table
Previous Message Greg Stark 2003-12-01 16:15:47 Re: Partitions implementation with views