Re: lastOverflowedXid does not handle transaction ID wraparound

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: Stan Hu <stanhu(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: lastOverflowedXid does not handle transaction ID wraparound
Date: 2021-10-20 11:00:35
Message-ID: 3F300306-D8B5-47F8-807E-6E6BF374ED52@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 17 окт. 2021 г., в 21:55, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> написал(а):
> I wonder what would be side
> effects of clearing it when the snapshot is not suboverfloved anymore?

I think we should just invalidate lastOverflowedXid on every XLOG_RUNNING_XACTS if subxid_overflow == false. I can't find a reason not to do so.

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Japin Li 2021-10-20 11:12:04 Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber
Previous Message Michael Paquier 2021-10-20 10:55:20 Re: [PATCH] Fix memory corruption in pg_shdepend.c