Re: FETCH FIRST clause WITH TIES option

From: Surafel Temesgen <surafel3000(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Subject: Re: FETCH FIRST clause WITH TIES option
Date: 2019-11-13 07:38:15
Message-ID: CALAY4q-QkLU7aYrtoa2fdOhwdmkvydgRbcxXAhUjcj=qH206ng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 11, 2019 at 5:56 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)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 *

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2019-11-13 07:55:15 Re: [proposal] recovery_target "latest"
Previous Message Michael Paquier 2019-11-13 07:34:49 Re: Coding in WalSndWaitForWal