Re: postgresql 9.6 - cannot freeze committed xmax
| От | Alexandre Garcia |
|---|---|
| Тема | Re: postgresql 9.6 - cannot freeze committed xmax |
| Дата | |
| Msg-id | CAPYLKR6Tybsp=_26HZ6MN_J1S9MUr2bHvgeROR+Jpy0EBN6j_w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: postgresql 9.6 - cannot freeze committed xmax (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: postgresql 9.6 - cannot freeze committed xmax
|
| Список | 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@anarazel.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
В списке pgsql-admin по дате отправления: