Horton

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

x4mmm@yandex-team.ru

View thread View on postgr.es
From: Andrey Borodin <x4mmm@yandex-team.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: a.pyhalov@postgrespro.ru, pgsql-bugs@lists.postgresql.org
Date: 2021-07-25T15:54:29Z
Lists: pgsql-bugs 

> 25 июля 2021 г., в 19:32, Tom Lane <tgl@sss.pgh.pa.us> написал(а):
> 
> 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.

Sorry for the noise. I did not know that suffixes for .out files work this way.

Best regards, Andrey Borodin.

Commits

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