From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Prevent instability in contrib/pageinspect's regression
 test.
In-reply-to: <3214376.1669051457@sss.pgh.pa.us>
References: <E1ox94a-000EHu-VH@gemulon.postgresql.org>
 <20221121172206.h6kywxrzqcmhoqom@awork3.anarazel.de>
 <3214376.1669051457@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Mon, 21 Nov 2022 12:24:17 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3215926.1669052115.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 21 Nov 2022 12:35:15 -0500
Message-ID: <3215927.1669052115@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3215927.1669052115%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> Andres Freund <andres@anarazel.de> writes:
>> Looks like a chunk of the buildfarm doesn't like this - presumably beca=
use
>> they use force_parallel_mode =3D regress. Seems ok to just force that t=
o off in
>> this test?

> Ugh ... didn't occur to me to try that.  I'll take a look.

Hmm, so the problem is:

SELECT octet_length(get_raw_page('test1', 'main', 0)) AS main_0;
ERROR:  cannot access temporary tables during a parallel operation

Why in the world is get_raw_page() marked as parallel safe?
It clearly isn't, given this restriction.

			regards, tom lane