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 C824C53669 for ; Thu, 24 Mar 2005 22:00:52 +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 83968-03 for ; Thu, 24 Mar 2005 22:00:43 +0000 (GMT) Received: from polaris.pinpointresearch.com (66-7-238-130.cust.telepacific.net [66.7.238.130]) by svr1.postgresql.org (Postfix) with ESMTP id 80EC35343D for ; Thu, 24 Mar 2005 22:00:42 +0000 (GMT) Received: from betelgeuse.pinpointresearch.com (betelgeuse.pinpointresearch.com [192.168.1.179]) by polaris.pinpointresearch.com (Postfix) with ESMTP id D27941038D; Thu, 24 Mar 2005 14:00:44 -0800 (PST) From: Steve Crawford Organization: Pinpoint Research To: Kris Kiger , Scott Marlowe Subject: Re: Very worried about this Date: Thu, 24 Mar 2005 14:00:44 -0800 User-Agent: KMail/1.5.1 Cc: "Pgsql-Admin (E-mail)" References: <42432F48.8060103@musicrebellion.com> <1111700264.12450.10.camel@state.g2switchworks.com> <424334DE.4020908@musicrebellion.com> In-Reply-To: <424334DE.4020908@musicrebellion.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503241400.44263.scrawford@pinpointresearch.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.084 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/410 X-Sequence-Number: 16908 On Thursday 24 March 2005 1:45 pm, 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. Try turning up logging to catch as much as possible (all statements, connections and everything). Don't know if it will yield a clue but it's a place to start. At least it might trap any statement, however generated, that is messing with the sequence if that turns out to be the culprit or alternately it might eliminate that possibility. Cheers, Steve