Re: [BUGS] Old row version in hot chain become visible after a freeze
| От | Peter Geoghegan |
|---|---|
| Тема | Re: [BUGS] Old row version in hot chain become visible after a freeze |
| Дата | |
| Msg-id | CAH2-Wzkx-=QZhNWRKLxHjzWbtEqfwYftSMT0XPwHC26GpvJHeg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [BUGS] Old row version in hot chain become visible after a freeze ("Wood, Dan" <hexpert@amazon.com>) |
| Список | pgsql-bugs |
On Thu, Aug 31, 2017 at 4:20 PM, Wood, Dan <hexpert@amazon.com> wrote:
> I was aware of the other one and, in fact, reverted the change just to make sure it wasn’t Involved. A strange
coincidenceindeed.
FWIW, the enhanced amcheck does actually detect this:
postgres=# select bt_index_check('t_pkey', true);
ERROR: XX000: failed to find parent tuple for heap-only tuple at
(0,3) in table "t"
LOCATION: IndexBuildHeapRangeScan, index.c:2597
The good news is that this happens in a codepath that is also used by REINDEX:
postgres=# reindex index t_pkey ;
ERROR: XX000: failed to find parent tuple for heap-only tuple at
(0,3) in table "t"
LOCATION: IndexBuildHeapRangeScan, index.c:2597
Perhaps the lack of field reports of this error suggests that it's
fairly rare. Very hard to be sure about that, though.
--
Peter Geoghegan
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: