pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
To: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Nisha Moond <nisha.moond412@gmail.com>
Cc: Gunnar Morling <gunnar.morling@googlemail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Unexpected behavior when setting "idle_replication_slot_timeout"
Date: Fri, 11 Jul 2025 08:48:11 +0900
Message-ID: <74ce2b9b-bafe-42b8-9d06-33cf1d233f80@oss.nttdata.com> (raw)
In-Reply-To: <90ebaa4554a5edaf1665cc0106612a8a9572abc1.camel@cybertec.at>
References: <CADGJaX_0+FTguWpNSpgVWYQP_7MhoO0D8=cp4XozSQgaZ40Odw@mail.gmail.com>
	<CAKFQuwYVEgy+fiHMvSoykiEef-VF-ZV9Gxv4rynk9NNK9UMPYQ@mail.gmail.com>
	<472687.1751731008@sss.pgh.pa.us>
	<474268.1751731988@sss.pgh.pa.us>
	<f12271e6aea3b87eaa430d0c9008ca1f3154c31e.camel@cybertec.at>
	<CAA4eK1JaYNQtTj5u-YP3G2UJbJoevD4PnUiM+sQy8DerjNPJFA@mail.gmail.com>
	<1cea80b2ed4f355ae6a68e36f56a1410b59ea4a8.camel@cybertec.at>
	<OSCPR01MB14966D811DB105E49289B8298F549A@OSCPR01MB14966.jpnprd01.prod.outlook.com>
	<2dcea297694d9ab8eafd1db70d385ec0b49e3d27.camel@cybertec.at>
	<49b70ae1-acbe-41ec-9d2d-8284b3462fc1@oss.nttdata.com>
	<9bda06ec9ad0a3e3df898dfb542db53b54b55368.camel@cybertec.at>
	<CAA4eK1J1Npia9J7zS4LzJqeO4uy5pcJ8BmzF7r1YeoFpa4-7jw@mail.gmail.com>
	<OS7PR01MB14968E808BF18FC2915D82671F548A@OS7PR01MB14968.jpnprd01.prod.outlook.com>
	<b69236c25061d5ee1e4fcd5fb7de1193db3f1338.camel@cybertec.at>
	<5fddbcc5-0c05-493d-a3f0-1fe49ffe5600@oss.nttdata.com>
	<90ebaa4554a5edaf1665cc0106612a8a9572abc1.camel@cybertec.at>



On 2025/07/10 20:58, Laurenz Albe wrote:
> On Thu, 2025-07-10 at 19:27 +0900, Fujii Masao wrote:
>> I created this as a separate patch from the one that changes the unit,
>> since they serve different purposes. Both patches are attached.
>> I'm planning to commit them.
> 
> Your Patches look good for me.

Thanks for the review! I've pushed both patches.

Regards,

-- 
Fujii Masao
NTT DATA Japan Corporation






view thread (38+ messages)  latest in thread

Message-ID: <74ce2b9b-bafe-42b8-9d06-33cf1d233f80@oss.nttdata.com>
Permalink:  ../74ce2b9b-bafe-42b8-9d06-33cf1d233f80@oss.nttdata.com/
Also on:    postgresql.org/message-id/74ce2b9b-bafe-42b8-9d06-33cf1d233f80@oss.nttdata.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: masao.fujii@oss.nttdata.com, laurenz.albe@cybertec.at, kuroda.hayato@fujitsu.com, amit.kapila16@gmail.com, tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, nisha.moond412@gmail.com, gunnar.morling@googlemail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: Unexpected behavior when setting "idle_replication_slot_timeout"
  In-Reply-To: <74ce2b9b-bafe-42b8-9d06-33cf1d233f80@oss.nttdata.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox