-
Notifications
You must be signed in to change notification settings - Fork 55
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
Postgres 16 upgrade #2655
Comments
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it. |
Postgres 14 (and 13) are out, and we're still on Postgres 12 - TimescaleDB 2.5 will support pg14 |
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
TimescaleDB is working on Postgres 15 support as well. I don't know if it makes sense at this point to wait and upgrade to Postgres 15 or just switch to 14? |
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it. |
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it. |
This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it. |
This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it. |
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it. |
One of the main motivators here is the ability to use |
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
@axelstudios - should we include this in our FY24Q2 bug fixes? |
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it. |
No description provided.
The text was updated successfully, but these errors were encountered: