| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | dshash_find_or_insert vs. OOM |
| Date: | 2026-03-17 23:34:17 |
| Message-ID: | CA+TgmoaJwUukUZGu7_yL74oMTQQz2=zqucMhF9+9xBmSC5us1w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
For most memory allocation primitives, we offer a "no OOM" version.
dshash_find_or_insert is an exception. Here's a small patch to fix
that. I have some interest in slipping this into v19 even though I am
submitting it quite late, because it would be useful for
pg_stash_advice[1]. Let me know what you think about that.
--
Robert Haas
EDB: http://www.enterprisedb.com
[1] As yet uncommitted. See pg_plan_advice thread.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-dshash-Make-it-possible-to-suppress-out-of-memory.patch | application/octet-stream | 8.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-03-18 01:33:55 | Re: dshash_find_or_insert vs. OOM |
| Previous Message | Gyan Sreejith | 2026-03-17 23:24:53 | Re: [Proposal] Adding Log File Capability to pg_createsubscriber |