Horton

Re: Reducing power consumption on idle servers

Thomas Munro <thomas.munro@gmail.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@gmail.com>
To: Simon Riggs <simon.riggs@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, Andres Freund <andres@anarazel.de>, Zheng Li <zhengli10@gmail.com>, Jim Nasby <nasbyj@amazon.com>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2022-11-30T03:49:22Z
Lists: pgsql-hackers 
On Wed, Nov 30, 2022 at 1:32 AM Simon Riggs
<simon.riggs@enterprisedb.com> wrote:
> Re-attaching patch for bgwriter and walwriter, so it is clear this is
> not yet committed.

I'm just curious, and not suggesting that 60s wakeups are a problem
for the polar ice caps, but why even time out at all?  Are the latch
protocols involved not reliable enough?  At a guess from a quick
glance, the walwriter's is but maybe the bgwriter could miss a wakeup
as it races against StrategyGetBuffer(), which means you might stay
asleep until the *next* buffer allocation, but that's already true I
think, and a 60s timeout is not much of a defence.

Commits

  1. Remove promote_trigger_file.

  2. Add pg_promote function

  3. pg_ctl promote