Jelte Fennema-Nio
Jelte Fennema-Nio
To help debug a bit more could you share the output of the following commands? 1. `pg_autoctl show state` 2. `pg_autoctl show settings` 3. `pg_autoctl show events` If you run...
FYI Tests are failing
I don't think this change is good in the current form. If you have the password set to NULL and set pg_hba.conf to only allow scram-sha-256 (or md5). Then postgres...
See also https://github.com/citusdata/pg_auto_failover/pull/672 which has similar errors.
I put an extra `log_debug` in the macro itself. This way file/line info should be shown there when using `-vv`.
There should be a test added that checks for this new behaviour.
When trying this out locally with `pg_autoctl stop --pgdata node1` (the primary). I got this error in the logs: ``` 12:26:10 18285 INFO pg_autoctl received signal SIGTERM, terminating 12:26:13 18288...
So the reason is that pg_auto_failover doesn't want to do an automatic failover unless it can guarantee no loss of reported committed data. With your settings it is not able...
I tried this, but I can't get it to work. What does your `.tern-project` file look like?
I just used the webpack plugin as I use that anyway, so I didn't have a need for this anymore.