X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5853C5374B for ; Thu, 24 Mar 2005 21:52:53 +0000 (GMT) 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 80369-07 for ; Thu, 24 Mar 2005 21:52:45 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id B43CE5370E for ; Thu, 24 Mar 2005 21:52:43 +0000 (GMT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j2OLqZhx034844 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 24 Mar 2005 14:52:37 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j2OLqYDZ033058; Thu, 24 Mar 2005 14:52:34 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j2OLqYDj033057; Thu, 24 Mar 2005 14:52:34 -0700 (MST) (envelope-from mfuhr) Date: Thu, 24 Mar 2005 14:52:34 -0700 From: Michael Fuhr To: Kris Kiger Cc: Scott Marlowe , "Pgsql-Admin (E-mail)" Subject: Re: Very worried about this Message-ID: <20050324215234.GA33036@winnie.fuhr.org> References: <42432F48.8060103@musicrebellion.com> <1111700264.12450.10.camel@state.g2switchworks.com> <424334DE.4020908@musicrebellion.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <424334DE.4020908@musicrebellion.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/408 X-Sequence-Number: 16906 On Thu, Mar 24, 2005 at 04:45:02PM -0500, Kris Kiger wrote: > I'm positive no one else has been in the database. There are two of us > who work on it and we have been side by side all afternoon. The problem > appears to be purely internal to the database. I'm running more tests > as we speak and we are still recieving the same sporadic errors. It > works for a long amount of time and then the error occurs, but then > things work fine again for a while. The inconsistency is quite troubling. What are the results of the following queries? SELECT max(d_id) FROM hd; SELECT * FROM hd_d_id_seq; -- Michael Fuhr http://www.fuhr.org/~mfuhr/