Finally got around to working out why this laptop wouldn't always sleep properly. Turns out, it was set to hibernate after 180 minutes asleep, even when plugged in. That particular setting is buried deep in the power plan settings, which is only accessible by running Control Panel manually and digging right down to the Sleep settings for the current power plan.
I set the thing to Hibernate after zero minutes of Sleep, and that has fixed it. I also added Hibernate to the main power menu, in case I should ever decide to use that. The W11 power settings are a complete failure of organisation and accessibility.
@JohnK.N. That seems to disable the ability to hibernate completely, which is not what I wanted. Also, it is not part of the W11 GUI, which was the second part of my point. Other than those two things, you nailed it.
I was prepared to put up with heaps of moved cheese, if they succeeded in removing Control Panel. They did not. In fact, they made things worse compared with W10.
At least I think advanced power settings were accessible from the GUI in W10, even though it opened a separate dialog box.
For example, when I lived in Texas I had a power plan where if I used 1,000 KWH or more a month my bill was $49. If I used less than that my bill was $49 + difference I didn't use in cents/kwh.
It was literally cheaper for me to run stuff 24/7 and leak power than to not
> The use of methamphetamine, better known as crystal meth, was particularly prevalent: A pill form of the drug, Pervitin, was distributed by the millions to Wehrmacht troops before the successful invasion of France in 1940.
Good day to you, database persons ! I'm looking for some advice on which tool is fastest to backup/restore postgres databases. I tried pg_dump and pg_restore and find it amazing how it takes so long for a 200mb database.
@SeanGallardy That's a very circumstencial question that is going to require some benchmarks/ comparison of a similar database size in a different system
Ah I found some info, seems you need to change database settings to make restores faster then change them back afterwards.
it looks like you have multiple actions all trying to modify the content of the repo kicked off by the same event (merge to main) - so they're going to clash.
