| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: HashAgg degenerate case |
| Date: | 2024-11-13 07:18:18 |
| Message-ID: | d21e370e702ac2eb52a159d0e24c5fc25dde7b21.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, 2024-11-12 at 15:15 -0800, Jeff Davis wrote:
> I attached a proof of concept patch, and it does add some complexity,
> but it's not terrible. If tuplehash is going to be used for large
> hash
> tables, I don't think we can hide the doubling nature from the caller
> forever, assuming that the caller can do something about it (like
> spill).
Previous version was incorrect, v2 attached, which is still rough, but
hopefully better.
Regards,
Jeff Davis
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-simplehash-add-grow_ok-to-API.patch | text/x-patch | 4.5 KB |
| v2-0002-HashAgg-avoid-unexpected-hash-table-growth-near-m.patch | text/x-patch | 11.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | RECHTÉ Marc | 2024-11-13 08:00:46 | Very long loop breaking logical replication walsender / walreceiver connection |
| Previous Message | Noah Misch | 2024-11-13 00:26:57 | Re: BUG #17821: Assertion failed in heap_update() due to heap pruning |