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: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, 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-05T15:10:10Z
Lists: pgsql-bugs 
On Saturday, July 5, 2025, Fujii Masao <masao.fujii@oss.nttdata.com> wrote:

>
> Do you see any serious downside to switching the unit to seconds? I don't
> think it introduces any serious issues. On the contrary, it gives users
> finer
> control over the timeout, and additionally works around the issue
> that we're discussing here.
>

I do not, and would rather we make the change.  Minutes are an
unconventional base unit for time in our world and should be avoided.

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.