| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Printing window function OVER clauses in EXPLAIN |
| Date: | 2025-03-10 01:17:35 |
| Message-ID: | CAApHDvoaqmWSgS4LKnwWAxHFomH2+9zTLnvs7Y1995xC6dzC1w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 10 Mar 2025 at 14:13, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Hmm, OK. Do you think it could be sensible to put Run Condition
> before Filter, then? On the same grounds of "keeping related
> things together", it could be argued that Run Condition is
> related to the Window property. Also, the Run Condition acts
> before the Filter does, if I've got my head screwed on straight.
Yes, directly after the "Window" property makes sense for the reason
you stated. Thanks for thinking of that.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-03-10 01:19:16 | Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET |
| Previous Message | David Rowley | 2025-03-10 01:14:01 | Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET |