Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3595964FC3E for ; Thu, 25 Sep 2008 10:24:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 97781-09 for ; Thu, 25 Sep 2008 10:24:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 70C6364FC3D for ; Thu, 25 Sep 2008 10:24:10 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m8PDO8GC005724; Thu, 25 Sep 2008 09:24:08 -0400 (EDT) To: "BJ Taylor" cc: pgsql-admin@postgresql.org Subject: Re: missing chunk number 0 for toast value In-reply-to: <3d78fcfd0809241446j326110c4p9907e04dbd10106b@mail.gmail.com> References: <3d78fcfd0809241132y14a832cai8b32bc32e936699e@mail.gmail.com> <10862.1222287999@sss.pgh.pa.us> <3d78fcfd0809241446j326110c4p9907e04dbd10106b@mail.gmail.com> Comments: In-reply-to "BJ Taylor" message dated "Wed, 24 Sep 2008 15:46:49 -0600" Date: Thu, 25 Sep 2008 09:24:08 -0400 Message-ID: <5723.1222349048@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/300 X-Sequence-Number: 30393 "BJ Taylor" writes: > We are using version 8.3.1. And to be precise, when I started the vacuum > (analyze), I started it as a cron job to run daily around midnight. The > next day I came in and checked on it and it was still running. Not thinking > that it would take more than a full 24 hours to run, I let it be, and the > next day I came in and the server started acting weird. I believe the > vacuum process continued to run, and a second vacuum process was started. > The server became unstable, and refused incoming connections. Unstable how? What error did you get on the refused connections? What was showing up in the postmaster log? > At which > point, I killed all vacuum processes, and restarted postgresql. How did you do that killing exactly? > I believe > it was somewhere during this process that the database became corrupted. I > am not certain what happens when two vacuum processes run at the same time. Nothing of interest, it's done all the time. > That may have been the problem, or it may not have. Or it may have been > that I killed the vacuum process in the middle of what it was doing. One > way or another, the problem that we have now, is that we are unable to get a > dump of the database for backups, and the database seems less stable than it > was previously (dropping connections, and refusing connections seemingly at > random). Again, what errors are you getting exactly, and what shows up in the postmaster log? regards, tom lane