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

From Thomas Munro
Subject Re: walsender performance regression due to logical decoding on standby changes
Date
Msg-id CA+hUKG+iywOmdiGMOegUXuVDQzhgpSx9c5vpzOvYUEVDu_gZBQ@mail.gmail.com
Whole thread Raw
In response to Re: walsender performance regression due to logical decoding on standby changes  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: walsender performance regression due to logical decoding on standby changes
List pgsql-hackers
On Fri, May 12, 2023 at 11:58 PM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
> Andres, rightly put it - 'mis-using' CV infrastructure. It is simple,
> works, and makes the WalSndWakeup() easy solving the performance
> regression.

Yeah, this seems OK, and better than the complicated alternatives.  If
one day we want to implement CVs some other way so that this
I-know-that-CVs-are-really-made-out-of-latches abstraction leak
becomes a problem, and we still need this, well then we can make a
separate latch-wait-list thing.



pgsql-hackers by date:

Previous
From: Kirk Wolak
Date:
Subject: PSQL Should \sv & \ev work with materialized views?
Next
From: Michael Paquier
Date:
Subject: Re: benchmark results comparing versions 15.2 and 16