public inbox for [email protected]
help / color / mirror / Atom feedFrom: Oliver Elphick <[email protected]>
To: Neil Conway <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: PostgreSQL hackers list <[email protected]>
Cc: [email protected]
Subject: Re: [HACKERS] initdb should create a warning message [was Re:
Date: Mon, 01 Dec 2003 07:29:57 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Sun, 2003-11-30 at 23:18, Neil Conway wrote:
> Oliver Elphick <[email protected]> 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.
People have a distressing tendency to want to shoot themselves in the
foot; and the somewhat unfortunate naming of those files contributes to
the problem. While it is satisfying to see stupidity properly rewarded,
it is more neighbourly at least to attempt to protect a fool from his
folly. It is also kinder to those who may be depending on him for the
protection of their data.
> 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.
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.
--
Oliver Elphick [email protected]
Isle of Wight, UK http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"Who is like unto thee, O LORD, among the gods? who is
like thee, glorious in holiness, fearful in praises,
doing wonders?" Exodus 15:11
view thread (16+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: [HACKERS] initdb should create a warning message [was Re:
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox