Re: FETCH FIRST clause WITH TIES option - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: FETCH FIRST clause WITH TIES option
Date
Msg-id 20191126150941.GA4161@alvherre.pgsql
Whole thread Raw
In response to Re: FETCH FIRST clause WITH TIES option  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: FETCH FIRST clause WITH TIES option  (Surafel Temesgen <surafel3000@gmail.com>)
List pgsql-hackers
I rebased this patch, and my proposed changes are in 0002.

Looking at the changes in ExecLimit, I'm wondering if it would be better
to add a new state to the state machine there -- instead of doing all
the work in duplicative code in the LIMIT_INWINDOW case, have that one
only save the current end-of-window tuple and jump to
LIMIT_WINDOWEND_WITH_TIE (or something) which then returns all tuples that
match the current one.  I think that would end up being cleaner.  Please
research.

Marking Waiting on Author.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: v.makarov@postgrespro.ru
Date:
Subject: [PATCH] Increase the maximum value track_activity_query_size
Next
From: Tom Lane
Date:
Subject: Re: benchmarking Flex practices