X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3F30FD1B433; Mon, 1 Dec 2003 07:31:03 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 50844-09; Mon, 1 Dec 2003 03:30:33 -0400 (AST) Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by svr1.postgresql.org (Postfix) with ESMTP id 82ED6D1B4B9; Mon, 1 Dec 2003 03:30:31 -0400 (AST) Received: from lfix.demon.co.uk ([80.177.205.209] helo=cerberus.lfix.co.uk) by anchor-post-32.mail.demon.net with esmtp (Exim 3.35 #1) id 1AQiVr-000CLr-0W; Mon, 01 Dec 2003 07:30:31 +0000 Received: from linda.lfix.co.uk ([192.168.1.1]) by cerberus.lfix.co.uk with esmtp (Exim 4.24) id 1AQiVn-0007Cy-Mg; Mon, 01 Dec 2003 07:30:27 +0000 Subject: Re: [HACKERS] initdb should create a warning message [was Re: From: Oliver Elphick To: Neil Conway Cc: Tom Lane , PostgreSQL hackers list , pgsql-docs@postgresql.org In-Reply-To: <874qwl4f8h.fsf@mailbox.samurai.com> References: <20031126043752.51857.qmail@web10804.mail.yahoo.com> <11414.1069826007@sss.pgh.pa.us> <1070231374.7719.2654.camel@linda.lfix.co.uk> <874qwl4f8h.fsf@mailbox.samurai.com> Content-Type: text/plain Organization: LFIX Limited Message-Id: <1070263797.7719.2662.camel@linda.lfix.co.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 01 Dec 2003 07:29:57 +0000 Content-Transfer-Encoding: 7bit X-LFIX-MailScanner: Found to be clean X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/1 X-Sequence-Number: 2161 On Sun, 2003-11-30 at 23:18, Neil Conway wrote: > Oliver Elphick 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 Oliver.Elphick@lfix.co.uk 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