Re: Maybe don't process multi xmax in FreezeMultiXactId() if it is already marked as invalid?

Поиск

Список

Период

Сортировка

От	Maxim Orlov
Тема	Re: Maybe don't process multi xmax in FreezeMultiXactId() if it is already marked as invalid?
Дата	18 июня 17:29:13
Msg-id	CACG=ezbB2q2wYZseBA5mcNKXZwamPRb2dzzqrRtJ37E=K7do2w@mail.gmail.com обсуждение исходный текст
Ответ на	Maybe don't process multi xmax in FreezeMultiXactId() if it is already marked as invalid? ("Anton A. Melnikov" <a.melnikov@postgrespro.ru>)
Ответы	Re: Maybe don't process multi xmax in FreezeMultiXactId() if it is already marked as invalid?
Список	pgsql-hackers

Hi!

Maybe, I'm too bold, but looks like a kinda bug to me. At least, I don't understand why we do not check the HEAP_XMAX_INVALID flag.

My guess is nobody noticed, that MultiXactIdIsValid call does not check the mentioned flag in the "first" condition, but it's all my speculation.

Does anyone know if there are reasons to deliberately ignore the HEAP_XMAX INVALID flag? Or this is just an unfortunate oversight.

PFA, my approach on this issue.

Best regards,

Maxim Orlov.

В списке pgsql-hackers по дате отправления:

От: Ashutosh Sharma
Дата: 18 июня, 17:28:26
Сообщение: Re: Truncation of mapped catalogs (whether local or shared) leads to server crash

От: Yura Sokolov
Дата: 18 июня, 17:31:15
Сообщение: Re: Suggest two small improvements for PITR.