Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091

Поиск
Список
Период
Сортировка
От tiamoh m
Тема Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091
Дата
Msg-id CAPsGGUrKHYNduUFKx9_3AoTt87kpOs_pWr6coviCw52kSkRtpQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091  (Laurenz Albe <laurenz.albe@cybertec.at>)
Список pgsql-admin
Thank you very much Laurenz Albe

On Wed, Jan 29, 2025 at 12:40 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Tue, 2025-01-28 at 16:46 -0500, tiamoh m wrote:
> I have been having this bizarre error in most of my postgresql clusters.
>
> I don't know if anyone has experienced this or has a solution ?

That happens when you are using LISTEN and NOTIFY, but your transactions
are so long that by the time the signal is delivered, the information
about the transaction is already gone.

Use shorter database transactions.

Yours,
Laurenz Albe

В списке pgsql-admin по дате отправления: