From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, 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-21 02:35:15 |
Message-ID: | 20200421023515.GC19613@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 16, 2020 at 03:11:51PM -0400, Tom Lane wrote:
> If we were going to go down the path of periodically logging warnings
> about old prepared transactions, some single-instance background task
> like the checkpointer would be a better place to do the work in. But
> I'm not really recommending that, because I agree with Robert that
> we just plain don't want this functionality.
I thought we would just emit a warning at boot time.
--
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 | David Rowley | 2020-04-21 03:03:18 | Re: Parallel Append can break run-time partition pruning |
Previous Message | Michael Paquier | 2020-04-21 02:25:05 | Re: 001_rep_changes.pl stalls |