Re: Re: Damage control for planner's get_actual_variable_endpoint() runaway - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: Damage control for planner's get_actual_variable_endpoint() runaway
Date
Msg-id 3258594.1669058118@sss.pgh.pa.us
Whole thread Raw
In response to Re: Damage control for planner's get_actual_variable_endpoint() runaway  (Andres Freund <andres@anarazel.de>)
Responses Re: Re: Damage control for planner's get_actual_variable_endpoint() runaway
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On November 21, 2022 10:44:17 AM PST, Simon Riggs <simon.riggs@enterprisedb.com> wrote:
>> Robert, something like this perhaps? limit on both the index and the heap.

> I don't think we should add additional code / struct members into very common good paths for these limits.

Yeah, I don't like that either: for one thing, it seems completely
unsafe to back-patch.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Prevent instability in contrib/pageinspect's regression test.
Next
From: Tom Lane
Date:
Subject: Re: Add 64-bit XIDs into PostgreSQL 15