On Fri, Oct 11, 2019 at 12:44 AM Daniel Wood wrote:
> > Actually, I take it back -- the looping part is not normal. The
> > btpo_next->btpo_next page has no business linking back to the
> > original/first deleted page you mentioned. That's just odd.
>
> btpo_next->btpo_next does NOT link directly
> On October 10, 2019 at 1:18 PM Peter Geoghegan wrote:
>
>
> On Thu, Oct 10, 2019 at 12:48 PM Daniel Wood wrote:
> > Update query stuck in a loop. Looping in _bt_moveright().
>
> You didn't say which PostgreSQL versions were involved, and if the
> database was ever upgraded using pg_upgrade.
On Thu, Oct 10, 2019 at 1:18 PM Peter Geoghegan wrote:
> You didn't say which PostgreSQL versions were involved, and if the
> database was ever upgraded using pg_upgrade. Those details could
> matter.
In case you weren't aware, contrib/amcheck should make detected and
diagnosing these kinds of pr
On Thu, Oct 10, 2019 at 12:48 PM Daniel Wood wrote:
> Update query stuck in a loop. Looping in _bt_moveright().
You didn't say which PostgreSQL versions were involved, and if the
database was ever upgraded using pg_upgrade. Those details could
matter.
> ExecInsertIndexTuples->btinsert->_bt_doin
Update query stuck in a loop. Looping in _bt_moveright().
ExecInsertIndexTuples->btinsert->_bt_doinsert->_bt_search->_bt_moveright
Mid Tree Node downlink path taken by _bt_search points to a BTP_DELETED Leaf.
btpo_next is also DELETED but not in the tree.
btpo_next->btpo_next is NOT deleted bu
