Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1m7fAw-0000K9-VY
	for pgsql-bugs@arkaria.postgresql.org; Sun, 25 Jul 2021 14:32:18 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1m7fAv-0001mA-Hy
	for pgsql-bugs@arkaria.postgresql.org; Sun, 25 Jul 2021 14:32:17 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1m7fAv-0001m1-Bc
	for pgsql-bugs@lists.postgresql.org; Sun, 25 Jul 2021 14:32:17 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1m7fAo-0008Ba-0Q
	for pgsql-bugs@lists.postgresql.org; Sun, 25 Jul 2021 14:32:16 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 16PEW6Of1336602;
	Sun, 25 Jul 2021 10:32:07 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrey Borodin <x4mmm@yandex-team.ru>
cc: a.pyhalov@postgrespro.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock()
 and pg_advisory_xact_lock_shared()
In-reply-to: <1ADF4719-DE3D-4198-BEBA-9E04A7F1E632@yandex-team.ru>
References: <17122-04f3c32098a62233@postgresql.org>
 <924498.1627056766@sss.pgh.pa.us> <1267153.1627163097@sss.pgh.pa.us>
 <1ADF4719-DE3D-4198-BEBA-9E04A7F1E632@yandex-team.ru>
Comments: In-reply-to Andrey Borodin <x4mmm@yandex-team.ru>
	message dated "Sun, 25 Jul 2021 14:34:46 +0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1336600.1627223526.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 25 Jul 2021 10:32:06 -0400
Message-ID: <1336601.1627223526@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/1336601.1627223526%40sss.pgh.pa.us>
Precedence: bulk

Andrey Borodin <x4mmm@yandex-team.ru> writes:
>> 25 =D0=B8=D1=8E=D0=BB=D1=8F 2021 =D0=B3., =D0=B2 02:44, Tom Lane <tgl@s=
ss.pgh.pa.us> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
>> +PREPARE TRANSACTION 'foo6';  -- fails
>> +ERROR:  prepared transactions are disabled
>> +HINT:  Set max_prepared_transactions to a nonzero value.

> Do we actually expect this particular error?

Of course.  "make installcheck" will produce that result file,
unless you've changed max_prepared_transactions on the server
being tested.

			regards, tom lane