| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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 18:06:29 |
| Message-ID: | 20200422180629.GN19613@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 22, 2020 at 01:05:17PM -0400, Robert Haas wrote:
> 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.
It is --- I was just thinking we should have a minimal native warning.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-04-22 18:06:41 | Re: design for parallel backup |
| Previous Message | Alvaro Herrera | 2020-04-22 17:57:54 | Re: 2pc leaks fds |