| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alexandre Garcia <alexandre(at)vmfarms(dot)com> |
| 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:16:22 |
| Message-ID: | 20180228211621.vikbp5s3rwg47455@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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 | Laurenz Albe | 2018-02-28 21:16:56 | Re: Reliable WAL file shipping over unreliable network |
| Previous Message | Alexandre Garcia | 2018-02-28 21:12:58 | Re: postgresql 9.6 - cannot freeze committed xmax |