From: | Chitra Creta <chitracreta(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 8.3 data corruption |
Date: | 2012-05-02 06:11:38 |
Message-ID: | CABkVLeOK+=dP2+hiwjs31zzE8V0tZcgWR=vK0KgMjtFtDXJ4Tg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello all,
Any thoughts on this one?
Cheers.
On Tue, May 1, 2012 at 9:51 PM, Chitra Creta <chitracreta(at)gmail(dot)com> wrote:
> Hi there,
>
> I have mission-critical data running on PostgreSQL 8.3. My database got
> corrupted a few days ago as I ran out of disk space.
>
> I had to run pg_resetxlog to get the database started again. I am now
> experiencing the following errors:
>
> 1. ERROR: t_xmin is uncommitted in tuple to be updated
>
> 2. ERROR: could not access status of transaction 61323662
> Detail: Could not read from file "pg_subtrans/03A7" at offset 188416: No
> error.
>
> Does anyone know how to resolve the issues above? Would a VACUUM FULL or a
> dump and restore work? Or is there another way to fix the above.
>
>
> Thanking you in advance,
> Chitra
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2012-05-02 06:26:38 | Re: PostgreSQL 8.3 data corruption |
Previous Message | Maxim Boguk | 2012-05-02 05:41:30 | Re: Inefficient plan selected by PostgreSQL 9.0.7 |