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

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: a(dot)pyhalov(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
Date: 2021-07-25 15:54:29
Message-ID: B1BE9035-0638-4337-AB4A-81036EB05137@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 25 июля 2021 г., в 19:32, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> написал(а):
>
> Andrey Borodin <x4mmm(at)yandex-team(dot)ru> writes:
>>> 25 июля 2021 г., в 02:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

In response to

Browse pgsql-bugs by date

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