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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
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 14:32:06
Message-ID: 1336601.1627223526@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Borodin 2021-07-25 15:54:29 Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()
Previous Message Andrey Borodin 2021-07-25 09:34:46 Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()