Support for newer postgres versions

[raqqun]

What would you like to be added:

Will stolon support postgres versions 16 and 17 ?

Why is this needed:

To keep compatibility with newer postgres versions.

[kedare]

I don't think it's still developed unfortunately, maybe consider switching to patroni.

[ctrix]

pr #926 does just this.

Support for newer postgres versions and more.

[sebasmannem]

@sgotti can I be a committer on this project?
Or would you be okay if I forked it and moved users to the fork?

[sgotti]

@sebasmannem Feel free to open pull requests. They should be smaller and reviewable and pass the tests. It's impossible to review and doesn't make sense opening a PR with tons of commits.

[sebasmannem]

Thank for getting back @sgotti.

I don't think the size of PR's is the big issue.

• I once contributed support --wal-dir in keeper #865 but you never merged it and I don't understand why.
• I also contributed enabling client certs #870 and we did not have much pulse on that either.
• Your latest release is more then 4 years old
• latest merged PR is of the maintainer, it is over 2 years ago
• pulse does not look good
• contributors page does not seem promising

The coomunity see's that too. The project really needs a revive.

I am thinking about:

• implementing a new unittest / e2e test framework that is open to everyone that wants to issue a PR
• adding a lot of other linting, simplified release management, etc.
• enabling dependabot and fixing all the issues it raises (just merging PR's by now)
• working with the contributors for merging all of the issued PR's together
• bringing down issues

I can help with that, but not by just issuing small PR's.

[sebasmannem]

@raqqun I use stolon in our solution called pgvillage, and that still works with postgres 16 and 17.