| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: A performance issue with Memoize |
| Date: | 2023-10-25 06:45:59 |
| Message-ID: | CAMbWs4_Axa6sxMx4f5jk-iiJwVio_jv8PJijDMf6-Hg2g8Cifw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 20, 2023 at 7:43 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:
> +1
>
> it would be great to fix this problem - I've seen this issue a few times.
>
Thanks for the input. I guess this is not rare in the real world. If
the subquery contains lateral reference to a Var that also appears in
the subquery's join clauses, we'd probably suffer from this issue.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2023-10-25 06:59:09 | Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements |
| Previous Message | Richard Guo | 2023-10-25 06:40:58 | Re: A performance issue with Memoize |