Re: DELETE ERROR: tuple concurrently updated

From: John R Pierce <pierce(at)hogranch(dot)com>
To: Михаил Кечинов <kechinoff(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: DELETE ERROR: tuple concurrently updated
Date: 2009-12-29 11:13:34
Message-ID: 4B39E45E.30603@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Михаил Кечинов wrote:
> 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.

where did you copy this data from if the drive died? if it was from a
previously made file system backup, was this backup made with some sort
of point-in-time volume snapshot capability, or was pg_start_backup()
called before it was made ?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Stark 2009-12-29 11:38:26 Re: DELETE ERROR: tuple concurrently updated
Previous Message Михаил Кечинов 2009-12-29 11:08:28 Re: DELETE ERROR: tuple concurrently updated