Re: Make wal_receiver_timeout configurable per subscription

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Japin Li <japinli(at)hotmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Make wal_receiver_timeout configurable per subscription
Date: 2026-02-06 04:32:36
Message-ID: CAHGQGwE2UfkDPvB+49SiXYbP7cArABhE9ADt_ANTt2Ba+Z4U0g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 6, 2026 at 10:50 AM Japin Li <japinli(at)hotmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo Nagata 2026-02-06 04:37:35 Re: Warn when creating or enabling a subscription with max_logical_replication_workers = 0
Previous Message Yugo Nagata 2026-02-06 03:54:14 Re: Show expression of virtual columns in error messages