Re: Should we remove vacuum_defer_cleanup_age?

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Alvaro Herrera <alvherre@alvh.no-ip.org>

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

Date: 2023-04-24T16:09:45Z

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 Mon, Apr 24, 2023 at 8:36 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> The one thing that IMO makes it less confusing is to have it return the
> value rather than modifying it in place.

Yeah, I don't understand why we have these functions that modify the
value in place. Those are probably convenient here and there, but
overall they seem to make things more confusing.

-- 
Robert Haas
EDB: http://www.enterprisedb.com