From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: a.pyhalov@postgrespro.ru
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
Date: Sun, 25 Jul 2021 10:32:06 -0400
Message-ID: <1336601.1627223526@sss.pgh.pa.us> (raw)
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>
Andrey Borodin <x4mmm@yandex-team.ru> writes:
>> 25 июля 2021 г., в 02:44, Tom Lane <tgl@sss.pgh.pa.us> написал(а):
>> +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
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, x4mmm@yandex-team.ru, 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: <1336601.1627223526@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