Re: Should we remove vacuum_defer_cleanup_age?

Jonathan S. Katz <jkatz@postgresql.org>

From: "Jonathan S. Katz" <jkatz@postgresql.org>

To: Laurenz Albe <laurenz.albe@cybertec.at>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Greg Stark <stark@mit.edu>

Cc: Robert Haas <robertmhaas@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Andres Freund <andres@anarazel.de>, Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@postgresql.org

Date: 2023-04-14T19:07:37Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Rework text in replication slots documentation
- 27d04ed5310a 17.0 landed
Remove vacuum_defer_cleanup_age
- 1118cd37eb61 16.0 landed
Allow read only connections during recovery, known as Hot Standby.
- efc16ea52067 9.0.0 cited

On 4/14/23 1:15 PM, Laurenz Albe wrote:

> Let's remove vacuum_defer_cleanup_age, and put a note in the release notes
> that recommends using statement_timeout and hot_standby_feedback = on
> on the standby instead.
> That should have pretty much the same effect, and it is measured in
> time and not in the number of transactions.

+1.

Jonathan