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

From: Neil Conway <neilc(at)samurai(dot)com>
To: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org
Subject: Re: [HACKERS] initdb should create a warning message [was Re:
Date: 2003-11-30 23:18:54
Message-ID: 874qwl4f8h.fsf@mailbox.samurai.com
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:
> The use of the word "log" in the directory name does tend to invite
> this error, and some have acted on it without asking first. I think
> initdb should put a README.IMPORTANT file in $PGDATA to say [...]

If someone deletes something from $PGDATA without understanding what
it is, they deserve what they get.

I do agree that we could stand to document the purpose of pg_clog
and pg_xlog more clearly. However, this information belongs in the
standard documentation, not scattered throughout $PGDATA.

-Neil

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message William Yu 2003-12-01 00:04:04 Re: filesystem suggestion for pg
Previous Message Oliver Elphick 2003-11-30 22:29:35 initdb should create a warning message [was Re: [ADMIN] Size on Disk]

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2003-12-01 04:48:04 Re: Numeric version of factorial()
Previous Message Oliver Elphick 2003-11-30 22:29:35 initdb should create a warning message [was Re: [ADMIN] Size on Disk]

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2003-11-30 23:42:53 Re: Was: Triggers, Stored Procedures, PHP
Previous Message Sailesh Krishnamurthy 2003-11-30 22:46:46 Re: Materialized views proposal