Re: Do we need to handle orphaned prepared transactions in the server? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Do we need to handle orphaned prepared transactions in the server?
Date
Msg-id CA+TgmoZ5Dh6AkO65jhVP8HBLtOZ0c_EeHVr_f0gbbwmnJ9b9kw@mail.gmail.com
Whole thread Raw
In response to Re: Do we need to handle orphaned prepared transactions in the server?  (Hamid Akhtar <hamid.akhtar@gmail.com>)
Responses Re: Do we need to handle orphaned prepared transactions in the server?  (Hamid Akhtar <hamid.akhtar@gmail.com>)
List pgsql-hackers
On Thu, Apr 16, 2020 at 4:43 AM Hamid Akhtar <hamid.akhtar@gmail.com> wrote:
> My real question is whether vacuum should be preemptively complaining about prepared transactions or stale
replicationslots rather than waiting for transaction id to exceed the safe limit. I presume by the time safe limit is
exceeded,vacuum's work would already have been significantly impacted. 

Yeah, for my part, I agree that letting things go until the point
where VACUUM starts to complain is usually bad. Generally, you want to
know a lot sooner. That being said, I think the solution to that is to
run a monitoring tool, not to overload the autovacuum worker with
additional duties.

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



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Making openssl_tls_init_hook OpenSSL specific
Next
From: Richard Guo
Date:
Subject: Re: sqlsmith crash incremental sort