| From: | Arne Roland <arne(dot)roland(at)malkut(dot)net> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com>, Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A performance issue with Memoize |
| Date: | 2024-01-18 06:39:09 |
| Message-ID: | 542c1950-2bea-4fc2-911c-b18c0ec5d62b@malkut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Richard,
I can tell this a real world problem. I have seen this multiple times in
production.
The fix seems surprisingly simple.
I hope my questions here aren't completely off. I still struggle to
think about the implications.
I wonder, if there is any stuff we are breaking by bluntly forgetting
about the subplan params. Maybe some table valued function scan within a
subquery scan? Or something about casts on a join condition, that could
be performed differently?
I wasn't able to construct a problem case. I might be just missing
context here. But I am not yet fully convinced whether this is safe to
do in all cases.
Regards
Arne
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2024-01-18 06:42:45 | Re: Reduce useless changes before reassembly during logical replication |
| Previous Message | Michael Paquier | 2024-01-18 06:17:26 | Re: heavily contended lwlocks with long wait queues scale badly |