From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Murawski <markm-lists@intellasoft.net>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Bug plperl.c
In-reply-to: <9acdf918-7fff-4f40-f750-2ffa84f083d2@intellasoft.net>
References: <9acdf918-7fff-4f40-f750-2ffa84f083d2@intellasoft.net>
Comments: In-reply-to Mark Murawski <markm-lists@intellasoft.net>
	message dated "Tue, 22 Feb 2022 12:49:26 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <821292.1645559302.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Tue, 22 Feb 2022 14:48:22 -0500
Message-ID: <821293.1645559302@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/821293.1645559302%40sss.pgh.pa.us>
Precedence: bulk

Mark Murawski <markm-lists@intellasoft.net> writes:
> Affects Versions: 12 (and probably all others)
> Steps to Reproduce:
> - Run a query during plperl validation -- ie: inside a warn handler
> 2022-02-22 12:17:04 EST -  -  -  - 12950 -  - 0 - LOG:  server process 
> (PID 19702) was terminated by signal 11: Segmentation fault

I couldn't reproduce this, either in HEAD or 12.10.  However, maybe
there's something faulty about your example, because in my hands it
doesn't seem that plperl_spi_exec is reached at all.

If we do need to do something here, my inclination would be to
reject execution of any SPI operations during validation.  That's
not a case that's supposed to have any side-effects.

			regards, tom lane