public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Alexander Kuzmenkov <[email protected]>
Cc: [email protected]
Subject: Re: Correct SQLSTATE for ENOMEM in file access
Date: Fri, 02 Feb 2024 15:20:13 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CALzhyqwg-atPhwH3jeNQdrnj5eP2mvx-TaBo3w1r82vzBrC9QA@mail.gmail.com>
References: <CALzhyqzgQph0BY8-hFRRGdHhF8CoqmmDHW9S=hMZ-HMzLxRqDQ@mail.gmail.com>
	<[email protected]>
	<CALzhyqwg-atPhwH3jeNQdrnj5eP2mvx-TaBo3w1r82vzBrC9QA@mail.gmail.com>

Alexander Kuzmenkov <[email protected]> writes:
> On Fri, Feb 2, 2024 at 8:12 PM Tom Lane <[email protected]> wrote:
>> Hmm, do you think this is actually reachable?  AFAIK we should only be
>> calling errcode_for_file_access() after functions that are unlikely to
>> report ENOMEM.

> It's reachable, that's how I noticed. I'm seeing logs like "XX000:
> could not load library \"/usr/lib/postgresql/15/lib/plpgsql.so\": out
> of memory" from internal_load_library and so on. Not sure what is the
> exact configuration required to reproduce this, probably at least the
> overcommit should be disabled.

OK, can't argue with experimental evidence ;-)

			regards, tom lane

view thread (3+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Correct SQLSTATE for ENOMEM in file access
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox