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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(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>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Damage control for planner's get_actual_variable_endpoint() runaway
Date: 2022-11-21 17:37:34
Message-ID: CA+TgmoaYgSOmmESR+7D+WKgh=ocRV7n0ipYAo1NKS2H99ed-Mw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 21, 2022 at 12:30 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> This can't quite be right - isn't this only applying the limit if we found a
> visible tuple?

It doesn't look that way to me, but perhaps I'm just too dense to see
the problem?

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-11-21 17:37:59 Re: Damage control for planner's get_actual_variable_endpoint() runaway
Previous Message sirisha chamarthi 2022-11-21 17:35:53 Re: Catalog_xmin is not advanced when a logical slot is lost