From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martin Butter <martin.butter@splendiddata.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17081: Segmentation fault on _PG_init() in a
 session_preload_library
In-reply-to: <5e9f75fd-2886-2b7d-0a8f-0b46049786f5@splendiddata.com>
References: <17081-b5a83245fd4e64bb@postgresql.org>
 <5e9f75fd-2886-2b7d-0a8f-0b46049786f5@splendiddata.com>
Comments: In-reply-to Martin Butter <martin.butter@splendiddata.com>
	message dated "Fri, 02 Jul 2021 09:15:02 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <807269.1625233817.1@sss.pgh.pa.us>
Date: Fri, 02 Jul 2021 09:50:17 -0400
Message-ID: <807270.1625233817@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/807270.1625233817%40sss.pgh.pa.us>
Precedence: bulk

Martin Butter <martin.butter@splendiddata.com> writes:
> Extension test_spi_in_preload_session just executes 'select 1' in its 
> _PG_init() function.
> Until Postgres version 14beta1 this works fine, but in version 14beta2 
> the process dies.

I don't believe we have ever considered that (i.e., execution of general
SQL from a _PG_init function) to be a supported case.  If it seemed to
work before, that was completely accidental.  There is no transaction
context in place when process_session_preload_libraries runs.

			regards, tom lane