Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 9595F632D49 for ; Wed, 7 Jul 2010 19:41:38 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 41871-02 for ; Wed, 7 Jul 2010 22:41:30 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.jfcomputer.com (unknown [76.14.161.106]) by mail.postgresql.org (Postfix) with ESMTP id 5816B632D2A for ; Wed, 7 Jul 2010 19:41:31 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by mail.jfcomputer.com (Postfix) with ESMTP id 0074179676 for ; Wed, 7 Jul 2010 15:41:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at jfcomputer.com Received: from mail.jfcomputer.com ([127.0.0.1]) by localhost (server1.jfcomputer.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kXgb0xo9DYd8 for ; Wed, 7 Jul 2010 15:41:27 -0700 (PDT) Received: from [192.168.1.219] (unknown [192.168.1.219]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: johnf@mail.jfcomputer.com) by mail.jfcomputer.com (Postfix) with ESMTPSA id 8BC9179647 for ; Wed, 7 Jul 2010 15:41:27 -0700 (PDT) From: John To: pgsql-sql@postgresql.org Subject: Re: strangest thing happened Date: Wed, 7 Jul 2010 15:41:27 -0700 User-Agent: KMail/1.9.9 References: <201007071259.03294.johnf@jfcomputer.com> <20100707204244.GB28181@rice.edu> <4C34FC50.6070203@magwerks.com> In-Reply-To: <4C34FC50.6070203@magwerks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <201007071541.27248.johnf@jfcomputer.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.792 tagged_above=-5 required=5 tests=BAYES_40=-0.001, RDNS_NONE=0.793 X-Spam-Level: X-Archive-Number: 201007/38 X-Sequence-Number: 34351 On Wednesday 07 July 2010 03:14:40 pm Justin Graf wrote: > I would be looking at the log files for the Inserts into that table as a > means to track down what is the cause. =C2=A0If there are no log files or > don't have enough detail, crank up the logging level and wait for it to > happen again??? That is scary - let it happen again???? I'm not keeping enough info in the= =20 log. I actually turned off most of the info the log files are gathering=20 because the system has been running for 6-7 months without an issue. I jus= t=20 got a call around noon telling me something was going wrong. That's when I= =20 discovered the sequences were the wrong values. I'm sure there has to be=20 some sort of real explanation - but I don't know what it is. Johnf