Re: DELETE ERROR: tuple concurrently updated - Mailing list pgsql-general

From Михаил Кечинов
Subject Re: DELETE ERROR: tuple concurrently updated
Date
Msg-id c8f0e27c0912290308l39d0ec36p5b6e608352e153f3@mail.gmail.com
Whole thread Raw
In response to Re: DELETE ERROR: tuple concurrently updated  (Greg Stark <gsstark@mit.edu>)
Responses Re: DELETE ERROR: tuple concurrently updated  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
Version 8.4
So, it was not database crash - HDD died. We copied data to new HDD, droped some dead indexes (when vacuuming we has errors with indexes, so we drop it and recreate new indexes), made vacuum full. That's all.

2009/12/29 Greg Stark <gsstark@mit.edu>
On Tue, Dec 29, 2009 at 9:41 AM, Михаил Кечинов <kechinoff@gmail.com> wrote:
> One week ago our database has crashed and after restore begins some
> problems.

What version?

And how was this backup taken? It sounds like it might be an
inconsistent backup.

--
greg



--
Михаил Кечинов
http://www.mkechinov.ru

pgsql-general by date:

Previous
From: Greg Stark
Date:
Subject: Re: DELETE ERROR: tuple concurrently updated
Next
From: John R Pierce
Date:
Subject: Re: DELETE ERROR: tuple concurrently updated