Horton
Menu

Re: Unexpected behavior when setting "idle_replication_slot_timeout"

David G. Johnston <david.g.johnston@gmail.com>

View thread
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Amit Kapila <amit.kapila16@gmail.com>, Fujii Masao <masao.fujii@oss.nttdata.com>, Nisha Moond <nisha.moond412@gmail.com>, Gunnar Morling <gunnar.morling@googlemail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-07-05T05:55:45Z
Lists: pgsql-bugs 
On Friday, July 4, 2025, Laurenz Albe <laurenz.albe@cybertec.at> wrote:

> One of the nice things about the Grand Unified
> Configuration is that you can use units different from the default.
>

Supplying the value as '2 h', SHOW will display 2h while
pg_settings.setting shows 120 (min).

David J.

Commits

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

  1. doc: Clarify meaning of "idle" in idle_replication_slot_timeout.

  2. Change unit of idle_replication_slot_timeout to seconds.