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.