Re: Row pattern recognition

From: Henson Choi <assam258(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>, jian(dot)universality(at)gmail(dot)com
Cc: zsolt(dot)parragi(at)percona(dot)com, sjjang112233(at)gmail(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, peter(at)eisentraut(dot)org, li(dot)evan(dot)chao(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Row pattern recognition
Date: 2026-09-28 04:55:15
Message-ID: CAAAe_zDb-EWizm8ijKxeXX5Brc8Pe3v+4jM_umg7xXJ-zVZK-g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Tatsuo,

> BTW, I plan to add a note to "9.23. Window Functions" in the
> PostgreSQL documentation, something like below to explicitly stat
> that the patch does not support the RUNNING keyword. Comments?

Looks good to me. Just one sentence to suggest:

> The SQL standard allows to put a keyword RUNNING in front of row
> pattern navigation functions FIRST and LAST.

"allows to put" reads awkwardly in English. How about matching the
first sentence of the nth_value note just above it ("The SQL standard
defines a FROM FIRST or FROM LAST option for nth_value."):

The SQL standard defines a RUNNING prefix for the row pattern
navigation functions FIRST and LAST.

Then the two notes also continue the same way, with "This is not
implemented in PostgreSQL." The rest reads fine as is.

Best regards,
Henson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-09-28 05:00:02 Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation
Previous Message Alexandre Felipe 2026-09-28 04:45:55 Re: aio: worker: Free SMGR objects when idle