RE: Unexpected behavior when setting "idle_replication_slot_timeout"

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
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:27:08
Message-ID: OS7PR01MB14968E808BF18FC2915D82671F548A@OS7PR01MB14968.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> > 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.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2025-07-10 05:51:36 Re: Unexpected behavior when setting "idle_replication_slot_timeout"
Previous Message Thomas Thai 2025-07-10 04:35:56 PostgreSQL 18 beta1 - Segmentation fault on custom type casting