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 1ADF4719-DE3D-4198-BEBA-9E04A7F1E632@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>)
Responses 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 г., в 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?

Best regards, Andrey Borodin.



pgsql-bugs by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
Next
From: Tom Lane
Date:
Subject: Re: BUG #17122: panic on prepare with subsequent pg_advisory_lock() and pg_advisory_xact_lock_shared()