Re: DELETE ERROR: tuple concurrently updated

From: Михаил Кечинов <kechinoff(at)gmail(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: DELETE ERROR: tuple concurrently updated
Date: 2009-12-29 11:08:28
Message-ID: c8f0e27c0912290308l39d0ec36p5b6e608352e153f3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)mit(dot)edu>

> On Tue, Dec 29, 2009 at 9:41 AM, Михаил Кечинов <kechinoff(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2009-12-29 11:13:34 Re: DELETE ERROR: tuple concurrently updated
Previous Message Greg Stark 2009-12-29 10:51:39 Re: DELETE ERROR: tuple concurrently updated