| From: | Dave Peticolas <dave(at)krondo(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: error in vacuum |
| Date: | 2018-09-02 01:31:01 |
| Message-ID: | CAPRbp047pUGj6GJLuBsJzc_YMGmSisYWmon_H_d+CE+O6XFkYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Sep 1, 2018 at 5:28 PM Dave Peticolas <dave(at)krondo(dot)com> wrote:
> On Sat, Sep 1, 2018, 5:10 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
> wrote:
>
>> On 09/01/2018 04:47 PM, Dave Peticolas wrote:
>> > I'm seeing this error on a table repeatedly:
>> >
>> > found update xid 3433096759 <(343)%20309-6759>
>> <tel:%28343%29%20309-6759> from before
>> > relfrozenxid 3498422955
>>
>> Where is this, your primary or the instance you are running from the
>> backup?
>>
>
> This is a primary, 9.6.8 to be exact.
>
> >
>> > What can I do to repair this table?
>>
>
One thing I tried on a database restored from a primary backup that
exhibits the same "found update xid" error is this:
1. pg_dump the table and its referencing tables.
2. truncate the table and its referencing tables.
3. Load the dump file.
Does that seem reasonable?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-09-02 01:56:02 | Re: error in vacuum |
| Previous Message | Dave Peticolas | 2018-09-02 00:53:04 | Re: locate DB corruption |