Re: lastOverflowedXid does not handle transaction ID wraparound
От | Stan Hu |
---|---|
Тема | Re: lastOverflowedXid does not handle transaction ID wraparound |
Дата | |
Msg-id | CAMBWrQkjs63=en7swzSodGhuuukq+nYfZEMtv1UtpYPfH3u2=w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: lastOverflowedXid does not handle transaction ID wraparound (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Ответы |
Re: lastOverflowedXid does not handle transaction ID wraparound
|
Список | pgsql-hackers |
On Wed, Oct 20, 2021 at 9:01 PM Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote: > > lastOverflowedXid is the smallest subxid that possibly exists but > possiblly not known to the standby. So if all top-level transactions > older than lastOverflowedXid end, that means that all the > subtransactions in doubt are known to have been ended. Thanks for the patch! I verified that it appears to reset lastOverflowedXid properly. I may not be understanding https://github.com/postgres/postgres/blob/dc899146dbf0e1d23fb24155a5155826ddce34c9/src/backend/storage/ipc/procarray.c#L1326-L1327 correctly, but isn't lastOverflowedXid the last subxid for a given top-level XID, so isn't it actually the largest subxid that possibly exists?
В списке pgsql-hackers по дате отправления: