| From: | Alexandre Garcia <alexandre(at)vmfarms(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: postgresql 9.6 - cannot freeze committed xmax |
| Date: | 2018-02-28 21:17:08 |
| Message-ID: | CAPYLKR6Tybsp=_26HZ6MN_J1S9MUr2bHvgeROR+Jpy0EBN6j_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Oh yes sorry => `ERROR: cannot freeze committed xmax 43076385` on that
same table
On Wed, Feb 28, 2018 at 4:16 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2018-02-28 21:12:58 +0000, Alexandre Garcia wrote:
> > Thanks for your answers, took me a little while to restore a backup from
> > before the upgrade on an empty 9.2 server but here we are =>
> > https://gist.github.com/kuuji/cc73c3c193a0d58aa0e651fbd7bfec58
>
> Thanks.
>
> > > > > Prod starting throwing the following errors during autovacuum ->
> > > 'cannot
> > > > > freeze committed xmax <xid>' on 2 different tables. Running vacuum
> > > manually
> > > > > revealed more tables affected by the same error.
>
> What's an example <xid> in that message that triggers for
> problematic_table? I need that to properly interpret the data you
> provided.
>
> Thanks,
>
> Andres
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MichaelDBA | 2018-02-28 21:21:29 | Re: Postgresql | Vacuum information |
| Previous Message | Laurenz Albe | 2018-02-28 21:16:56 | Re: Reliable WAL file shipping over unreliable network |