Re: Exit walsender before confirming remote flush in logical replication

From: "Vitaly Davydov" <v(dot)davydov(at)postgrespro(dot)ru>
To: "Greg Sabino Mullane" <htamfids(at)gmail(dot)com>
Cc: "Kyotaro Horiguchi" <horikyota(dot)ntt(at)gmail(dot)com>, andres(at)anarazel(dot)de, amit(dot)kapila16(at)gmail(dot)com, kuroda(dot)hayato(at)fujitsu(dot)com, smithpb2250(at)gmail(dot)com, osumi(dot)takamichi(at)fujitsu(dot)com, pgsql-hackers(at)postgresql(dot)org, sawada(dot)mshk(at)gmail(dot)com, michael(at)paquier(dot)xyz, peter(dot)eisentraut(at)enterprisedb(dot)com, dilipbalaut(at)gmail(dot)com
Subject: Re: Exit walsender before confirming remote flush in logical replication
Date: 2025-09-26 11:10:02
Message-ID: 1a9d89-68d67480-1b-29edfa00@90613631
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Greg, All

I'm interested in walsender shutdown mode option as well. Unexpected waiting for
wal sender shutdown in fast mode creates some problems to follow a SLA. I also
propose to create a GUC which can be used to set the shutdown mode globally.
Once, the original author was not responded for some time, I like the idea to
create a new separate patch for walsender shutdown mode based on the work in
this thread. I'm ready to participate in patch preparation and testing.

With best regards,
Vitaly

On Tuesday, September 17, 2024 15:29 MSK, Greg Sabino Mullane <htamfids(at)gmail(dot)com> wrote:

> Thanks for everyone's work on this, I am very interested in it getting into
> a release. What is the status of this?
>
> My use case is Patroni - when it needs to do a failover, it shuts down the
> primary. However, large transactions can cause it to stay in the "shutting
> down" state for a long time, which means your entire HA system is now
> non-functional. I like the idea of a new flag. I'll test this out soon if
> the original authors want to make a rebased patch. This thread is old, so
> if I don't hear back in a bit, I'll create and test a new one myself. :)
>
> Cheers,
> Greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-09-26 11:12:11 Re: Proposal: Conflict log history table for Logical Replication
Previous Message shveta malik 2025-09-26 10:14:36 Re: Improve pg_sync_replication_slots() to wait for primary to advance