Re: walsender performance regression due to logical decoding on standby changes - Mailing list pgsql-hackers

From Andres Freund
Subject Re: walsender performance regression due to logical decoding on standby changes
Date
Msg-id 20230509210024.4lfcb2wzrcijzaba@awork3.anarazel.de
Whole thread Raw
In response to Re: walsender performance regression due to logical decoding on standby changes  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: walsender performance regression due to logical decoding on standby changes
List pgsql-hackers
Hi,

On 2023-05-09 13:38:24 -0700, Jeff Davis wrote:
> On Tue, 2023-05-09 at 12:02 -0700, Andres Freund wrote:
> > I don't think the approach of not having any sort of "registry" of
> > whether
> > anybody is waiting for the replay position to be updated is
> > feasible. Iterating over all walsenders slots is just too expensive -
> 
> Would it work to use a shared counter for the waiters (or, two
> counters, one for physical and one for logical), and just early exit if
> the count is zero?

That doesn't really fix the problem - once you have a single walsender
connected, performance is bad again.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Feature: Add reloption support for table access method
Next
From: Stephen Frost
Date:
Subject: Re: Large files for relations