X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id ACC7AD7B9E for ; Tue, 15 Nov 2005 21:26:12 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 46867-01 for ; Wed, 16 Nov 2005 01:26:15 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by svr1.postgresql.org (Postfix) with ESMTP id 33153D7D3D for ; Tue, 15 Nov 2005 21:26:10 -0400 (AST) Received: from nmd.esds.den.wayport.net (nmd.esds.den.wayport.net [64.134.13.30]) by svr2.postgresql.org (Postfix) with ESMTP id D971AF0BA4 for ; Wed, 16 Nov 2005 01:26:13 +0000 (GMT) Received: from nmd.esds.den.wayport.net (localhost [[UNIX: localhost]]) by nmd.esds.den.wayport.net (8.12.10/8.12.10) with ESMTP id jAG1Q69O029456; Tue, 15 Nov 2005 18:26:07 -0700 Message-ID: <437A8B0F.8020805@commandprompt.com> Date: Tue, 15 Nov 2005 17:27:43 -0800 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: tshipley@deru.com Cc: pgsql-hackers@postgresql.org Subject: Re: [ADMIN] Major Problem, need help! Can't run our website! References: <227C7FFACEA9D9118BD600096BA5A7CA011E188B@EIBPOST> <43795A96.9070500@proximity.com.au> <200511151627.02275.tshipley@deru.com> In-Reply-To: <200511151627.02275.tshipley@deru.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[MANY_EXCLAMATIONS=0, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200511/777 X-Sequence-Number: 76059 > > Renaming the file sounds like an excellent design decision since the current > name is a proven "human factor" bug. > I am sorry, but as soon as you look at the files it is obvious that they are not "just" log files. If someone is going to delete the xlog they are going to do it no matter what we call it. Unless of course we change the directory to pg_xlogs_do_not_ever_delete, but I doubt that would help either. Sincerely, Joshua D. Drake > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match >