Re: Reducing power consumption on idle servers
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Simon Riggs <simon.riggs@enterprisedb.com>,
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>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2023-01-24T20:39:39Z
Lists: pgsql-hackers
Thomas Munro <thomas.munro@gmail.com> writes: > Yeah, I definitely want to fix it. I just worry that 60s is so long > that it also needs that analysis work to be done to explain that it's > OK that we're a bit sloppy on noticing when to wake up, at which point > you might as well go to infinity. Yeah. The perfectionist in me wants to say that there should be explicit wakeups for every event of interest, in which case there's no need for a timeout. The engineer in me says "but what about bugs?". Better a slow reaction than never reacting at all. OTOH, then you have to have a discussion about whether 60s (or any other ice-cap-friendly value) is an acceptable response time even in the presence of bugs. It's kind of moot until we've reached the point where we can credibly claim to have explicit wakeups for every event of interest. I don't think we're very close to that today, and I do think we should try to get closer. There may come a point of diminishing returns though. regards, tom lane
Commits
-
Remove promote_trigger_file.
- cd4329d9393f 16.0 landed
-
Add pg_promote function
- 10074651e335 12.0 cited
-
pg_ctl promote
- 4695da5ae97b 9.1.0 cited