Re: Suppressing useless wakeups in walreceiver

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, alvherre(at)alvh(dot)no-ip(dot)org, bharath(dot)rupireddyforpostgres(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Suppressing useless wakeups in walreceiver
Date: 2022-11-15 04:49:16
Message-ID: 20221115044916.GA1906820@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Another option might be to just force initial reply/feedback messages when
streaming starts. The attached patch improves src/test/recovery test
runtime just like the previous one I posted.

On Mon, Nov 14, 2022 at 11:01:27AM -0800, Nathan Bossart wrote:
> I wonder if we
> ought to do something similar in the ConfigReloadPending path in case
> hot_standby_feedback is being turned on.

Looking closer, I see that a feedback message is forced in this case

Nathan Bossart
Amazon Web Services:

Attachment Content-Type Size
send_initial_reply_v2.patch text/x-diff 537 bytes

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-11-15 04:58:29 Re: [PoC] Improve dead tuple storage for lazy vacuum
Previous Message Andrey Borodin 2022-11-15 03:44:24 Re: libpq compression (part 2)