Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae
| От | Peter Geoghegan |
|---|---|
| Тема | Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae |
| Дата | |
| Msg-id | CAH2-WzmO-GPN8kpSCWzkq27FRk8xCBoDKJcMqVTYC+Dt8s4ZDQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae
Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae |
| Список | pgsql-bugs |
On Thu, May 16, 2024 at 12:38 PM Andres Freund <andres@anarazel.de> wrote: > I'm wondering if there was index processing, due to the number of tuples. And > if so, what type of indexes. There'd need to be something that could lead to > new snapshots being acquired... Did you ever see this theory of mine, about B-Tree page deletion + recycling? See: https://www.postgresql.org/message-id/flat/CAH2-Wz%3DzLcnZO8MqPXQLqOLY%3DCAwQhdvs5Ncg6qMb5nMAam0EA%40mail.gmail.com#d058a6d4b8c8fa7d1ff14349b3a50c3c (And related nearby emails from me.) It looked very much like index vacuuming was involved in some way when I actually had the opportunity to use gdb against an affected production instance that ran into the problem. -- Peter Geoghegan
В списке pgsql-bugs по дате отправления: