| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | ojford(at)gmail(dot)com, vik(at)postgresfriends(dot)org, pgsql-hackers(at)postgresql(dot)org, andrew(at)tao11(dot)riddles(dot)org(dot)uk, david(at)fetter(dot)org, krasiyan(at)gmail(dot)com |
| Subject: | Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options |
| Date: | 2025-01-20 00:18:25 |
| Message-ID: | 20250120.091825.2096861757587451701.ishii@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
>>> The latest version restricts it to lag, lead, first_value, last_value,
>>> and nth_value. We can extend it in a subsequent patch if there's
>>> demand?
>
>> The restriction is required by the SQL standard. So I don't think we
>> need to extend to other window functions.
>
> The SQL spec does not believe that user-defined window functions are a
> thing. So its opinion on this point is useless.
Of course the standard does not mention anything about the user
defined window functions and the restriction is not apply to the user
defined window functions.
> I would think that
> IGNORE NULLS is potentially useful for user-defined window functions,
> and we should not be building anything that restricts the feature to
> specific functions.
So you want to allow to use IGNORE NULLS to other built-in window
functions?
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Koshi Shibagaki (Fujitsu) | 2025-01-20 00:26:01 | RE: Replace current implementations in crypt() and gen_salt() to OpenSSL |
| Previous Message | Tom Lane | 2025-01-20 00:07:03 | Re: attndims, typndims still not enforced, but make the value within a sane threshold |