Re: Unexpected behavior when setting "idle_replication_slot_timeout"

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Gunnar Morling <gunnar(dot)morling(at)googlemail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Unexpected behavior when setting "idle_replication_slot_timeout"
Date: 2025-07-10 05:51:36
Message-ID: b69236c25061d5ee1e4fcd5fb7de1193db3f1338.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 2025-07-10 at 05:27 +0000, Hayato Kuroda (Fujitsu) wrote:
> > > The "hybrid approach" saves the two seconds on system with injection points,
> > > but cannot simplify the code.
> >
> > I feel that would be a needless complexity in the test.
>
> Yeah, it is the down side of the approach. If it do not have enough advantage, let's drop the idea.

Great, then I think that we have consensus.
Let's change to seconds and leave the injectsion points and tests as they are.

I'd still like to see the documentation improved, like my patch tried to do.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Kapila 2025-07-10 07:03:37 Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
Previous Message Hayato Kuroda (Fujitsu) 2025-07-10 05:27:08 RE: Unexpected behavior when setting "idle_replication_slot_timeout"