Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id E23EF6323EB for ; Fri, 16 Apr 2010 16:21:06 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 52546-04 for ; Fri, 16 Apr 2010 19:20:52 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gx0-f214.google.com (mail-gx0-f214.google.com [209.85.217.214]) by mail.postgresql.org (Postfix) with ESMTP id 20D856323E3 for ; Fri, 16 Apr 2010 16:20:56 -0300 (ADT) Received: by gxk6 with SMTP id 6so1580105gxk.14 for ; Fri, 16 Apr 2010 12:20:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=XBmNZsJHIftm9cCfu+HsJALR9gh8tTCkLzerb9NlN14=; b=pYFJkr25HyRCOv+SL2pQO/Nja4RLwZE0XnVMndcEdY7c49B49zE2NVmvpJ9jMz4BvO d9sA6u8v2e1Gov8g0mRsSabiJrOeUxmPqQINGDaC7IFLT9U3y9/eElL8a6w0ZPFGE3/2 HlwzDPw6z+cj316NsT966zcp0gzRmT6W6Scpk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=fvTHCDGeZGt/XxOjHfpManWfiabS2Fed4CrHiCjFrmmyV1+BaS3O5FmXvawjFt+l72 ntdXdnrLBH8BTkXy+H3TYm0BrApNDCVvqYWd6iJRdet/k9MCuRU1dStLN7Bm0XsaWarU cEsmrZ+tf5xo4HdtmWSAZ3YZQSqmvqWCMzj3U= MIME-Version: 1.0 Received: by 10.150.218.9 with HTTP; Fri, 16 Apr 2010 12:20:54 -0700 (PDT) In-Reply-To: <4BC8B0CE.2010401@ipso.ca> References: <4BC8639C.4010202@ipso.ca> <9048.1271429162@sss.pgh.pa.us> <4BC8A623.8090201@ipso.ca> <4BC8638E0200002500030A01@gw.wicourts.gov> <4BC8B0CE.2010401@ipso.ca> Date: Fri, 16 Apr 2010 13:20:54 -0600 Received: by 10.150.209.21 with SMTP id h21mr1847682ybg.118.1271445654690; Fri, 16 Apr 2010 12:20:54 -0700 (PDT) Message-ID: Subject: Re: Vacuum Full (PG 8.1) - Urgent help needed - Cancel & transaction "liberation" From: Scott Marlowe To: Alexandre Leclerc Cc: pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.087 tagged_above=-10 required=5 tests=AWL=-0.187, BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201004/226 X-Sequence-Number: 34320 On Fri, Apr 16, 2010 at 12:47 PM, Alexandre Leclerc wrot= e: > Le 2010-04-16 14:18, Kevin Grittner a =E9crit : >> >> Alexandre Leclerc =A0wrote: >> >> >>> >>> At some point I got: >>> ERROR: xlog flush request AC/FBEEF148 is not satisfied --- flushed >>> only to AC/FB9224A8 >>> CONTEXT: writing block 0 of relation 1664/0/1214 >>> WARNING: could not writing block 0 of 1664/0/1214 >>> DETAIL: Multiple failures --- write error may be permanent. >>> >> >> You're not running out of disk space where that writes, are you? >> > > There is 32 GB free. > >> >> >>> >>> It looks like the vacuum command does not want to be execute. The >>> other VACUUM is still progressing on the main database in another >>> postgres.exe shell. >>> >> >> Wait -- are you saying you're running two postgres instances against >> the same data directory at the same time? =A0(I sure hope not.) >> > > I did. :( Shame on me. I just realised while reading doc on postgres that= it > is not made for that but only for a single instance at the time. I hope I > did not break anything. You've almost certainly corrupted the data store. This is why you should always make a complete file system backup with the postmaster stopped before you start doing rescue work.