Re: Damage control for planner's get_actual_variable_endpoint() runaway

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Damage control for planner's get_actual_variable_endpoint() runaway
Date: 2022-11-21 17:34:31
Message-ID: 20221121173431.GW11463@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

This patch version runs "continue" unconditionally (rather than
conditionally, like the previous version).

if (!index_fetch_heap(index_scan, tableslot))
continue; /* no visible tuple, try next index entry */

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-11-21 17:35:15 Re: pgsql: Prevent instability in contrib/pageinspect's regression test.
Previous Message Andres Freund 2022-11-21 17:30:48 Re: Damage control for planner's get_actual_variable_endpoint() runaway