dshash_find_or_insert vs. OOM - Mailing list pgsql-hackers

From Robert Haas
Subject dshash_find_or_insert vs. OOM
Date
Msg-id CA+TgmoaJwUukUZGu7_yL74oMTQQz2=zqucMhF9+9xBmSC5us1w@mail.gmail.com
Whole thread
Responses Re: dshash_find_or_insert vs. OOM
Re: dshash_find_or_insert vs. OOM
List 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

pgsql-hackers by date:

Previous
From: Gyan Sreejith
Date:
Subject: Re: [Proposal] Adding Log File Capability to pg_createsubscriber
Next
From: Chao Li
Date:
Subject: Re: dshash_find_or_insert vs. OOM