From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: eng.khaledghazy@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
Date: Tue, 27 Jun 2023 17:44:57 -0400
Message-ID: <1053466.1687902297@sss.pgh.pa.us> (raw)
In-Reply-To: <20230627212423.p56zxuqeh5kyatqg@awork3.anarazel.de>
References: <18003-4c21ad729e8208ee@postgresql.org>
<20230627212423.p56zxuqeh5kyatqg@awork3.anarazel.de>
Andres Freund <andres@anarazel.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.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, eng.khaledghazy@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
In-Reply-To: <1053466.1687902297@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox