Re: Do we need to handle orphaned prepared transactions in the server?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Kellerer <shammat(at)gmx(dot)net>
Subject: Re: Do we need to handle orphaned prepared transactions in the server?
Date: 2020-04-22 17:05:17
Message-ID: CA+TgmoYR60M3BhszMJFvM1KRmuUAQTvD325yOEAG22YKMTB9PA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 21, 2020 at 6:10 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I thought if something was wrong, they might look at the server logs
> after a restart, or they might have a higher probability of having
> orphaned prepared transactions after a restart.

Maybe slightly, but having a monitoring tool like check_postgres.pl
for this sort of thing still seems like a vastly better solution.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-04-22 17:18:06 Re: More efficient RI checks - take 2
Previous Message Robert Haas 2020-04-22 16:29:57 Re: design for parallel backup