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-05T14:40:49Z
Lists: pgsql-hackers 
On Thu, Feb 5, 2026 at 1:06 PM Japin Li <japinli@hotmail.com> wrote:
> Thanks for updating the patches.
> I have one small comment on v4-0002:

Thanks for the review!


> @@ -104,6 +105,7 @@ typedef struct SubOpts
>         int32           maxretention;
>         char       *origin;
>         XLogRecPtr      lsn;
> +       char       *wal_receiver_timeout;
>  } SubOpts;
>
> According to the comment above the SubOpts struct:
>
>         Structure to hold a bitmap representing the user-provided CREATE/ALTER
>         SUBSCRIPTION command options and the parsed/default values of each of them.
>
> Since `wal_receiver_timeout` is a GUC-style interval value (typically stored as
> integer milliseconds), wouldn't it be better to use an int32 here instead of a
> string?

The wal_receiver_timeout value in CREATE SUBSCRIPTION can include a unit
(for example, 10s), not just a plain integer. Because of that, we can't store it
in an int32, 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.