| From: | Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Ewan Young <kdbase(dot)hack(at)gmail(dot)com> |
| Subject: | Re: Disallow outer-level and WHERE-clause aggregates in GRAPH_TABLE |
| Date: | 2026-09-01 01:08:44 |
| Message-ID: | CAN12+YKqJoz41Zz2QVbT_ZjQcwS0bVEn_rGdu8Kw2C7_vj9WwA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sorry for the spam.
I made one small change here. I don't think gprlevelsup is a good
name for the new leveling field. It should be called varlevelsup,
because in this patch it is really just carrying query levelsup in
the same sense as Var.varlevelsup.
Using gprlevelsup here suggests GRAPH_TABLE leveling, which
is a different thing. If we later support nested subqueries inside
GRAPH_TABLE, we will need a separate level to correlate an inner
GRAPH_TABLE with an outer one.
--
Sami Imseih
Amazon Web Services (AWS)
| Attachment | Content-Type | Size |
|---|---|---|
| v8-0001-Rework-GRAPH_TABLE-aggregate-window-SRF-rejection.patch | application/octet-stream | 28.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Xuneng Zhou | 2026-09-01 01:17:31 | Re: timeout value overflow in wait for lsn |
| Previous Message | Jeff Davis | 2026-09-01 00:45:30 | Re: Commit Sequence Numbers and Visibility |