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 09:34:46
Message-ID: 1ADF4719-DE3D-4198-BEBA-9E04A7F1E632@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 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?

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next 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()
Previous Message Etsuro Fujita 2021-07-25 08:55:38 Re: The case when AsyncAppend exists also in the qual of Async ForeignScan