On Mon, 21 Nov 2022 at 18:17, Andres Freund <and...@anarazel.de> wrote: > > Hi, > > On November 21, 2022 9:37:34 AM PST, Robert Haas <robertmh...@gmail.com> > wrote: > >On Mon, Nov 21, 2022 at 12:30 PM Andres Freund <and...@anarazel.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? > > The earlier version didn't have the issue, but the latest seems to only limit > after a visible tuple has been found. Note the continue; when fetching a heap > tuple fails.
Agreed, resolved in this version. Robert, something like this perhaps? limit on both the index and the heap. -- Simon Riggs http://www.EnterpriseDB.com/
0001-Damage-control-for-planner-s-get_actual_variable_end.v2.patch
Description: Binary data