Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared() - Mailing list pgsql-bugs

From Andrey Borodin
Subject Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
Date
Msg-id B1BE9035-0638-4337-AB4A-81036EB05137@yandex-team.ru
Whole thread Raw
In response to Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
Next
From: Heikki Linnakangas
Date:
Subject: Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows