Re: Infinite loop in GetMultiXactIdMembers() on 9.3.5 (involves pg_upgrade)
Вложения
В списке pgsql-bugs по дате отправления:
| От | David Gould |
|---|---|
| Тема | Re: Infinite loop in GetMultiXactIdMembers() on 9.3.5 (involves pg_upgrade) |
| Дата | |
| Msg-id | 20150128020954.67c90837@jekyl.lan обсуждение |
| Ответ на | Re: Infinite loop in GetMultiXactIdMembers() on 9.3.5 (involves pg_upgrade) (Peter Geoghegan <pg@heroku.com>) |
| Список | pgsql-bugs |
On Tue, 27 Jan 2015 19:56:43 -0800 Peter Geoghegan <pg@heroku.com> wrote: > I've since found BUG #11264, which seems to be the same issue...don't > know how I missed that one before. I see that Alvaro committed > something that at least addresses the non-interruptibility issue > directly, with a call to CHECK_FOR_INTERRUPTS() (commit d45e8dc52). > But I don't see any follow up addressing the bug itself, which I'd > hoped for. Did the discussion of BUG #11264 simply trail off without > an adequate resolution, as it appeared to? Sadly yes. I have hit the same problem and expect others will too. Alvaro suggested updating datminmxid to the oldest relminmxid will prevent this. I have written a script to do this, but not quite finished it as I was unsure what to do with the cases where nextMultiXactId in pg_controldata is < min(relminmxid) without looking at it more closely. I have attached the script (work in progress) in hopes it is useful or that someone can clarify how to calculate the correct datminmxid. -dg -- David Gould 510 282 0869 daveg@sonic.net If simplicity worked, the world would be overrun with insects.
В списке pgsql-bugs по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера