| From: | Dave Peticolas <dave(at)krondo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: error in vacuum |
| Date: | 2018-09-02 02:02:18 |
| Message-ID: | CAPRbp06mCsAOgs=McBcKYoKXvM1MQ+5_gNwG3cb5Y+k9LLLTOg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Sep 1, 2018 at 6:56 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dave Peticolas <dave(at)krondo(dot)com> writes:
> >>> I'm seeing this error on a table repeatedly:
> >>> found update xid 3433096759 <(343)%20309-6759> from before
> relfrozenxid 3498422955
>
> >> This is a primary, 9.6.8 to be exact.
>
> This message is known to be associated with several data-corruption bugs
> we've fixed recently. You should update to current (9.6.10) sooner not
> later. I don't think that will cure existing corruption for you, but
> it should prevent things from getting worse.
>
Ok, thank you for that information I will do so. The dump/truncate/restore
I mentioned in a later post seems to fix the corruption in a restored DB.
Given the nature of the bug do you think that would fix that table?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-09-02 02:24:01 | Re: error in vacuum |
| Previous Message | Tom Lane | 2018-09-02 01:56:02 | Re: error in vacuum |