Missing llvm_leave_fatal_on_oom() call

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Missing llvm_leave_fatal_on_oom() call
Date: 2023-02-21 14:50:53
Message-ID: 54b78cca-bc84-dad8-4a7e-5b56f764fab5@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

llvm_release_context() calls llvm_enter_fatal_on_oom(), but it never
calls llvm_leave_fatal_on_oom(). Isn't that a clear leak?

(spotted this while investigating
https://www.postgresql.org/message-id/a53cacb0-8835-57d6-31e4-4c5ef196de1a@deepbluecap.com,
but it seems unrelated)

- Heikki

Attachment Content-Type Size
fix-fatal-on-oom-leak.patch text/x-patch 360 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2023-02-21 15:16:33 Re: refactoring relation extension and BufferAlloc(), faster COPY
Previous Message Önder Kalacı 2023-02-21 14:25:10 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher