Dimitri Fontaine

> I think we count intended restarts as bad restarts for some reason. The supervisor is designed to be very simple, it does not distinguish between exit status codes when...

It seems weird but also restarting the process 5 times in a row in less than 5 mins (default service max time) seems weird too. I'm still not clear that...

Pull Request #734 introduces `SUPERVISOR_EXIT_ERROR` and `SUPERVISOR_EXIT_FATAL` situations with exit codes `EXIT_CODE_DROPPED` and `EXIT_CODE_FATAL`. We should be able to re-use that addition to distinguish more cases and improve error handling...

Hi @changchichung ; I think we're going to explore how to best solve major upgrades with `pg_upgradecluster` at a later point in time. Another candidate for automating upgrades uses logical...

See also #853 that lead us to using pg_basebackup tar format (maybe even tar.gz) when fetching the data, prior to swapping it in PGDATA. It makes the reasoning about necessary...

> 1. We add the `--auth-host` and `--auth-local` flags. > 2. If they are specified we use those values > 3. If `--auth-local` is not specified we use `trust` >...

After a chat with Onder, we are coming to the following conclusions: - the monitor is now an embedded database, not expected to be used or even usable for anything...

The first tutorial is already heavy in `az ...` commands, we spend a non-trivial amount of time setting up the stage for the demo. This second tutorial is even worse,...

> Agreed that all those az commands obscure the content. However bundling them in the pg_autoctl tool sounds like a confusing mixture of concerns. First, as a potentially vendor-neutral tool,...

We might want to retire this image from the documentation. Maybe we have to replace it with something new, but in any case, I'm not sure we want to maintain...