Re: Should we remove vacuum_defer_cleanup_age?

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>

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

Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Greg Stark <stark@mit.edu>, 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-20T22:51:54Z

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 Fri, Apr 14, 2023 at 03:07:37PM -0400, Jonathan S. Katz wrote:
> +1.

+1.  I agree with the upthread discussion and support removing
vacuum_defer_cleanup_age.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com