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 D510853404 for ; Thu, 24 Mar 2005 22:01:24 +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 84843-02 for ; Thu, 24 Mar 2005 22:01:23 +0000 (GMT) Received: from titan.internal (dsl093-203-229.ind1.dsl.speakeasy.net [66.93.203.229]) by svr1.postgresql.org (Postfix) with ESMTP id 6B56453401 for ; Thu, 24 Mar 2005 22:01:23 +0000 (GMT) Received: from [10.0.1.102] (helo=[10.0.1.102] ident=kris) by titan.internal with asmtp (Exim 4.34 #1 (Debian)) id 1DEaOF-0007Mm-Kp; Thu, 24 Mar 2005 17:01:19 -0500 Message-ID: <424338B1.9050501@musicrebellion.com> Date: Thu, 24 Mar 2005 17:01:21 -0500 From: Kris Kiger User-Agent: Mozilla Thunderbird 0.9 (X11/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Fuhr Cc: Scott Marlowe , "Pgsql-Admin (E-mail)" Subject: Re: Very worried about this References: <42432F48.8060103@musicrebellion.com> <1111700264.12450.10.camel@state.g2switchworks.com> <424334DE.4020908@musicrebellion.com> <20050324215234.GA33036@winnie.fuhr.org> In-Reply-To: <20050324215234.GA33036@winnie.fuhr.org> 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, hits=0.05 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/411 X-Sequence-Number: 16909 Heh, I see. The sequence currval was set lower than what was already in the table. It just so happened we had holes in our data for the values it was selecting. Thanks for pointing that out! Kris Michael Fuhr wrote: >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; > > >