Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 1BDD3636DAA for ; Sat, 21 Feb 2009 04:43:35 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 31223-09 for ; Sat, 21 Feb 2009 04:43:30 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by mail.postgresql.org (Postfix) with ESMTP id A1C4C6330DF for ; Sat, 21 Feb 2009 04:43:30 -0400 (AST) Received: from mailsrv2.i.zmi.at (h081217054243.dyn.cm.kabsi.at [81.217.54.243]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mailsrv2.i.zmi.at", Issuer "power4u.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id C076441E0 for ; Sat, 21 Feb 2009 09:43:28 +0100 (CET) Received: from saturn.localnet (saturn.i.zmi.at [10.0.0.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mailsrv2.i.zmi.at (Postfix) with ESMTPSA id 764AF40016F for ; Sat, 21 Feb 2009 09:43:28 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: 8.3.5 broken after power fail SOLVED Date: Sat, 21 Feb 2009 09:43:19 +0100 User-Agent: KMail/1.10.3 (Linux/2.6.27.13-ZMI; KDE/4.1.3; x86_64; ; ) References: <43a3a0bccd3684972f33e0051b45f2b4@webmail.zmi.at> In-Reply-To: <43a3a0bccd3684972f33e0051b45f2b4@webmail.zmi.at> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart12360272.ECuhZMBKnX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200902210943.27875@zmi.at> 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: 200902/164 X-Sequence-Number: 31385 --nextPart12360272.ECuhZMBKnX Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I managed to recover the data that was still readable. About 650=20 messageblock entries got lost. What makes me nervous a bit is that=20 postgres kept running despite (partially) being destroyed. It should=20 really have shutdown itself after the first problem was found. That=20 database is for mails, and I would understand to have lost some from the=20 time before the power loss, but I even lost entries from *after* the=20 crash. That means the error happened after the system was up again and=20 happily did it's work, but lost entries to a table. Could there be a=20 better way to check the db at crash recovery startup time? If someone is interested, I have a full postgres log with every single=20 command done to the database. mfg zmi =2D-=20 // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4 --nextPart12360272.ECuhZMBKnX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkmfvq8ACgkQzhSR9xwSCbQzDgCgombKh4vzju5pQ+mPRj7CsnTz qUIAoIa1ukUaYRw6VxgXwEeQTiG+h+3t =DROE -----END PGP SIGNATURE----- --nextPart12360272.ECuhZMBKnX--