-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
receiver/postgresql: bump PostgreSQL minimal supported version to latest official supported #30923
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I'm in support of this. Let's leave the issue open for a couple weeks so others can weigh in. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
No one has argued otherwise. I suggest we initially add a deprecation warning to the changelog, then remove in a subsequent version. |
Created following PR for adding a deprecation notice in the changelog: #32093 |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
receiver/postgresql
Is your feature request related to a problem? Please describe.
I see that this receiver is marked as supporting PG 9.6+ in the README. Do we still want to keep this much backwards compatibility given that this is quite an old, and unsupported for 2+ years, version now (list of PG versions here). It seems that the latest supported version is PG 12 with still ~9 months of support and we should maybe align on this?
This can make improvements, using more recent features (a bit?) harder or use less maintained/out-of-date modules versions (e.g. #30831)
Describe the solution you'd like
Update the prerequisites requirements for using this receiver (+ integration tests) to the latest officially supported PostgreSQL version
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: