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.

[sysblade]

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.

[swiftxy]

pr #926 does just this.

Support for newer postgres versions and more.

I noticed that this PR contains a lot of commits/changes. It's a bit difficult for me to identify which specific parts are the adaptations for the latest PostgreSQL version.

Would it be possible to separate the support for the new PG version into a standalone PR? This would make it much easier for me to pull down and verify on my terminal.

[sebasmannem]

Okay, @sgotti I started some fixes in github.com/pgvillage-tools/stolon.
There is a lot there:

160 files changed, 14351 insertions(+), 7752 deletions(-)

Mainly because:

• I replaced ci and cd to be github action native. No small task
• I have replaced old modules (2017) with new modules (recent), again, no small task.
• I have a smoke test, which is very cool and works awesome
• I use github actions for releasing as well

I am willing to slice this up into smaller chunks and upstream, but I don't think they will be 'small' per se.
Let me know if you are willing to collaborate. For now I am doing awesome stuff in my own repo.

@anyone else, ping me if you are interested in running stolon with uptodate code.

@swiftxy , @raqqun My smoke test runs with PG14-17 and I didn't need to do anything special to make it work with PG17.
So you can still use this version or use mine. Whichever you prefer.