| From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Subject: | Re: Commitfest 2023-03 starting tomorrow! |
| Date: | 2023-04-21 07:17:15 |
| Message-ID: | 20230421091715.3f32c54e@karst |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
After catching up with this thread, where pending bugs are listed and discussed,
I wonder if the current patches trying to lower the HashJoin memory explosion[1]
could be added to the "Older bugs affecting stable branches" list of
https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items as I think they
deserve some discussion/triage for v16?
The patch as it stands is not invasive. As I wrote previously[2], if we
couldn't handle such situation better in v16, and if this patch is not
backpatch-able in a minor release, then we will keep living another year, maybe
more, with this bad memory behavior.
Thank you,
[1] https://www.postgresql.org/message-id/20230408020119.32a0841b%40karst
[2] https://www.postgresql.org/message-id/20230320151234.38b2235e%40karst
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2023-04-21 07:34:42 | Improve list manipulation in several places |
| Previous Message | Nikita Malakhov | 2023-04-21 07:14:01 | Re: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns |