Horton
Menu

Re: Make wal_receiver_timeout configurable per subscription

Fujii Masao <masao.fujii@gmail.com>

View thread
From: Fujii Masao <masao.fujii@gmail.com>
To: Japin Li <japinli@hotmail.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Amit Kapila <amit.kapila16@gmail.com>, vignesh C <vignesh21@gmail.com>, Michael Paquier <michael@paquier.xyz>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-02-06T04:32:36Z
Lists: pgsql-hackers 
On Fri, Feb 6, 2026 at 10:50 AM Japin Li <japinli@hotmail.com> wrote:
> If we stored it as an integer, an input such as '1min' would be normalized to
> 60000 (milliseconds) and lose its unit.
>
> That would make it inconsistent with the original user input shown in pg_subscription.
> So we keep it as a string, right?

Yes, I think.

Regards,

-- 
Fujii Masao

Commits

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

  1. Add per-subscription wal_receiver_timeout setting.

  2. Make GUC wal_receiver_timeout user-settable.