Re: Database corruption event, unlockable rows, possibly bogus virtual xids? Invalid backend server xid

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ned Wolpert <ned(dot)wolpert(at)imemories(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Database corruption event, unlockable rows, possibly bogus virtual xids? Invalid backend server xid
Date: 2013-02-21 21:06:01
Message-ID: 3721.1361480761@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ned Wolpert <ned(dot)wolpert(at)imemories(dot)com> writes:
> Event: Running 9.1.6 with hot-standby, archiving 4 months of wal files,
> and even a nightly pg_dump all. 50G database. Trying to update or delete a
> row in a small (21 row, but heavily used table) would lock up completely.
> Never finish. Removed all clients, restarted the db instance, no joy. Check
> pg_stat_activity, and nothing that wasn't idle.... run the delete, locked
> up.

I'm betting one of those prepared transactions had updated or deleted
this row, and thus held a row lock on it. (Come to think of it, a
SELECT FOR UPDATE/SHARE might have been enough.) Did you try committing
or rolling back those xacts?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ned Wolpert 2013-02-21 22:35:39 Re: Database corruption event, unlockable rows, possibly bogus virtual xids? Invalid backend server xid
Previous Message Adrian Klaver 2013-02-21 21:02:40 Re: Need help extripating plpgsql