Re: 9.6.11- could not truncate directory "pg_serial": apparent wraparound

From: Pavel Suderevsky <psuderevsky(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: 9.6.11- could not truncate directory "pg_serial": apparent wraparound
Date: 2019-04-09 13:00:56
Message-ID: CAEBTBzuargmanLhZUpiUf=_15b8zTZ8LY6oA0Ry0SVF3-jde7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> On Sun, Apr 7, 2019 at 2:31 AM Pavel Suderevsky <psuderevsky(at)gmail(dot)com>
> wrote:
> > Probably if you advise me what could cause "pg_serial": apparent
> wraparound messages I would have more chances to handle all the performance
> issues.
>
> Did you see that warning at some point before the later error?
>
Thomas,

Thank you for your reply!

No, there have never been such warnings.

I wonder if this condition required you to have a serializable
> transaction running (or prepared) while you consume 2^30 AKA ~1
> billion xids. I think it is unreachable in v11+ because commit
> e5eb4fa8 allowed for more SLRU pages to avoid this artificially early
> wrap.

Do I understand right that this is about Virtual txids? Have no idea how
even a something close to a billion of transaction ids could be consumed on
this system.

--
Pavel Suderevsky
E: psuderevsky(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-04-09 13:42:05 Re: Logical replication failed recovery
Previous Message Achilleas Mantzios 2019-04-09 10:10:34 Re: Transactions