Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: eng(dot)khaledghazy(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
Date: 2023-06-28 00:03:52
Message-ID: 20230628000352.ik6txj62pqsfu7rm@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2023-06-27 17:44:57 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > That's not going to help you / the reporter, but to make issues like this
> > easier to debug in the future, I think we should
> > a) install an error context in load_libraries() printing the GUC name and
> > b) install an error context in internal_load_library() printing the name of
> > the shared library name
>
> +1. I'm not sure this specific issue justifies it, but it seems like that
> might make it easier to diagnose other shared-library-load-time issues
> as well.

I started a separate thread on -hackers for that topic. See
https://www.postgresql.org/message-id/20230628000307.rf6jnv4v4zyf6dqg%40awork3.anarazel.de

Greetings,

Andres Freund

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2023-06-28 03:18:00 Re: BUG #17949: Adding an index introduces serialisation anomalies.
Previous Message Michael Paquier 2023-06-27 23:19:15 Re: BUG #18000: Access method used by matview can be dropped leaving broken matview