| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Subject: | Use BumpContext contexts for TupleHashTables' tablecxt |
| Date: | 2025-10-26 20:55:11 |
| Message-ID: | 2268409.1761512111@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[ starting a new thread to keep this separate from the estimation
issue ]
I looked at the callers of BuildTupleHashTable, and realized that
(a) every one of them can use a BumpContext for the "tablecxt",
and (b) Jeff Davis already noticed that for nodeAgg.c, in commit
cc721c459. So we have precedent for the idea working. Here's
a fleshed-out patch to fix the remaining callers.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Use-BumpContext-contexts-for-TupleHashTables-tabl.patch | text/x-diff | 4.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2025-10-26 21:03:23 | Re: High CPU consumption in cascade replication with large number of walsenders |
| Previous Message | Tom Lane | 2025-10-26 20:16:20 | Re: Should HashSetOp go away |