Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issue #495 not fixed in 0.12.0, with postgres 9.6 #780

Open
WalkerWalker opened this issue Mar 27, 2023 · 1 comment
Open

issue #495 not fixed in 0.12.0, with postgres 9.6 #780

WalkerWalker opened this issue Mar 27, 2023 · 1 comment

Comments

@WalkerWalker
Copy link

WalkerWalker commented Mar 27, 2023

please check the lastest comment at #495 (comment)

Essentially the problem is fixed in 0.10.0 but not in 0.12.0, possibly due to #747 ?

If it can be confirmed, please reopen the issue. Thank you so much.

@WalkerWalker WalkerWalker changed the title issue #495 not fixed in 0.12.0 issue #495 not fixed in 0.12.0, with postgres 9.6 Mar 27, 2023
@sysadmind
Copy link
Contributor

My comment on the other thread below. I'm not opposed to adding the support, but it needs some thought on how we architect it so that we can maintain this project long term.

It would appear that support for postgres < 10 was missed in that PR. Postgres 9 is not a version that we test against in our CI system. It's end of support so we don't go out of our way to test on it, but we don't intentionally break compatibility when we can avoid it. I think we could add that second query back to support < 10, but it would require some work to architect a maintainable system to handle different queries for different server versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants