Re: FETCH FIRST clause WITH TIES option
Surafel Temsgen <surafel3000@gmail.com>
From: Surafel Temesgen <surafel3000@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Andrew Gierth <andrew@tao11.riddles.org.uk>
Date: 2019-11-13T07:38:15Z
Lists: pgsql-hackers
On Mon, Nov 11, 2019 at 5:56 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > First, I noticed that there's a significant unanswered issue from Andrew > Gierth about this using a completely different mechanism, namely an > implicit window function. I see that Robert was concerned about the > performance of Andrew's proposed approach, but I don't see any reply > from Surafel on the whole issue. > > i don't know much about window function implementation but am sure teaching window function about limit and implementing limit *variant on top of it will not be much simpler * *and performant than the current implementation. i also think more appropriate place to * *include limit variant is limitNode not other place which can case redundancy and * *maintainability issue * *regards * *Surafel *
Commits
-
Support FETCH FIRST WITH TIES
- 357889eb17bb 13.0 landed