Horton

Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
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
Date: 2021-07-25T14:32:06Z
Lists: pgsql-bugs 
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

Commits

  1. Fix check for conflicting session- vs transaction-level locks.