Re: Why we still see some reports of "could not access transaction status"
В списке pgsql-hackers по дате отправления:
| От | Michael Paesold |
|---|---|
| Тема | Re: Why we still see some reports of "could not access transaction status" |
| Дата | |
| Msg-id | 007b01c4b1b5$83b30140$ad01a8c0@zaphod обсуждение исходный текст |
| Ответ на | Why we still see some reports of "could not access transaction status" (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
Tom Lane wrote: > Having seen a couple recent reports of "could not access status of > transaction" for old, not-obviously-corrupt transaction numbers, I went > looking to see if I could find a way that the system could truncate CLOG > before it's really marked all occurrences of old transaction numbers as > known-dead or known-good. > > I found one. I was starting to wonder about those reports, too. Actually I was thinking about bringing this up as soon as I would find time. So I am glad you picked that up yourself -- and found a problem already. > I think what we ought to do to solve this problem permanently is to stop ... > > Comments? Well, I am not able to comment here, but I can say I usually trust your judgement. Best Regards, Michael Paesold
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера