viggy28
viggy28
Okay, Yeah should read that twice. Instead of doing it from right, I was doing from left. Thanks.
I don't think it's a stolon bug. You should reset the password a) either encrypted https://www.postgresql.org/docs/current/sql-alteruser.html or b) don't log the password reset statement.
I encountered this when I had the wrong `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID`.
there is also [https://hub.docker.com/r/bitnami/wal-g/](https://hub.docker.com/r/bitnami/wal-g/)
FWIW, I export `WALG_PGP_KEY_PATH` with the location of the PGP key stored in ASCII format and it works.
I agree, but its a feature request. Not sure, whether it needs to be under issues !!
Hi Team, wondering any updates on this? Anything I can help with to get this merged?
Sure @lawrencejones. Looks like you have done most of the work. Thanks much. Trying to understand what is needed. 1. https://github.com/sorintlab/stolon/pull/644/files#r293416129 2. https://github.com/sorintlab/stolon/pull/644#pullrequestreview-249368918 is unresolved but @sgotti also mentioned here...
Thanks @rnaveiras. Sorry about the delay. The challenge is how does one manage when there is a failover? Manually, creating and dropping slots is more maintenance. Also, leaving an inactive...
Is that problem exist for `can-be-synchronous-replica` flag too? The reason I ask is they both look like a similar flag and were introduced during the same commit.