Alexander Kukushkin
Alexander Kukushkin
Hi @waynerv, are you going to work on a fix?
No. Instead we need to restrict calculated values here: https://github.com/patroni/patroni/blob/3c07410695bbae28a493b23119bcbe826eb9e5bc/patroni/utils.py#L1107-L1121 and here: https://github.com/patroni/patroni/blob/3c07410695bbae28a493b23119bcbe826eb9e5bc/patroni/utils.py#L1066-L1075 I did some research for Linux and found following maximum possible values: - TCP_KEEPIDLE: 32767 - TCP_KEEPINTVL:...
> patroni.dcs.etcd3.Unknown: Seems to be a culprit, and maybe we can retry in this case, but **etcd 3.3.25** is quite old (almost 4 years) and I am pretty sure there...
> I'm using the newest version of etcd which available in ubuntu 22.04. It will take some time until I'm switching to Ubuntu 24.04 which uses 3.4.30. I am sorry,...
Our upgrade scripts are doing the heavy lifting: executing pg_upgrade and upgrading replicas with rsync. In addition to that the script is taking care of very specific spilo configuration. If...
Something is fishy. Backup script and pg_upgrade are supposed to be called from a `postgres` user. Do you happen to run containers without root? If yes, than the fix would...
> Yes, I'm running the operator as a non root user. Like how it's setup by default. I am talking about Spilo
In PostgreSQL the SELECT query could call volatile function and therefore execute a transaction. 1. It is not possible to figure out whether the specific SELECT is safe to execute...
We've also encountered this one in the wild. The problem seems to be related to timescaledb calling ExecCheckRTPerms() or ExecCheckPermissions() from copy_constraints_and_check(). https://github.com/pgaudit/pgaudit/pull/250 looks like a potential fix.