timescaledb
timescaledb copied to clipboard
[Enhancement]: Support PostgreSQL 15
What type of enhancement is this?
Other
What subsystems and features will be improved?
Platform/OS
What does the enhancement do?
Add support for PostgreSQL 15. Add more items if you discover problems that needs to be solved for the PG 15 release.
- [x] #3957
- [ ] [PG15]: Fix grants for bootstrap of data nodes
- [ ] [PG15]: Make TimescaleDB build from source
- [ ] [PG15]; Create PG-version specific tests
Implementation challenges
At the time of filing this issue, PostgreSQL 15 is still in progress so we should be careful about in what order we handle compatibilities. We should first focus on areas that are "stable" (in the sense that we do not expect changes in the code before the release), but wait with "unstable" parts of the code (where we suspect that there can be more changes).
PG15 features to be mindful of
- enable_group_by_reordering GUC, see https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=db0d67db2401eb6238ccc04c6407a4fd4f985832 Could affect the planning of our queries. We should make sure our queries are executed as expected regardless of this flag value.
- MERGE support, we should at least add some tests to make sure it works properly with hypertables, see https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=7103ebb7aae8ab8076b7e85f335ceb8fe799097c and https://www.depesz.com/2022/03/31/waiting-for-postgresql-15-add-support-for-merge-sql-command/
- SQL/JSON standard support. Probably doesn't affect us. There were many commits, here is a good summary: -- https://www.depesz.com/2022/03/31/waiting-for-postgresql-15-sql-json-constructors/ -- https://www.depesz.com/2022/04/01/waiting-for-postgresql-15-is-json-predicate/ -- https://www.depesz.com/2022/04/06/waiting-for-postgresql-15-json_table/
- Improvements in the logical replication. You can now specify exact columns to replicate and use WHERE conditions. Probably doesn't affect TSDB but is something we could use on Cloud. See https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=923def9a533a7d986acfb524139d8b9e5466d0a5 and https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=52e4f0cd472d39d07732b99559989ea3b615be78
- pgstat: store statistics in shared memory. This was a large refactoring but is unlikely to affect us too much. See https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a0ffa885e478f5eeacc4e250e35ce25a4740c487 and several previous commits.
Hi, PostgreSQL 15 is in Beta 3 already, any news on when TimescaleDB will be compatible?
Hi, PostgreSQL 15 is in Beta 3 already, any news on when TimescaleDB will be compatible?
We're working on this already and trying our best to make it available on the next release.
Hi. Do you have any estimations on the next release?
Are you aware of the problem this poses for Linux distributions? Alpine Linux v3.17 is gonna be released tomorrow, the default PostgreSQL version is 15 and now I have to either remove TimescaleDB from the v3.17, or apply unreleased patches to add support for PostgreSQL 15 and hope it will not screw up user databases.
Support for PG15 is progressing well, expect some news soon.
We will need to update this page in docs when PG15 support is ready.
Any update on this? Perhaps a speculation on when the support for PG15 will be available?
I installed postgresql15 from arch linux AUR and then compiled timescaledb 2.9.1 myself and did a couple of quick tests. so far it works flawlessly!
All open stuff from above link for psql15 are already merged so give it a go! No need to wait for the official release for it.
@jeffreymonroe @ivanfeanor @jirutka
@fboerman I think maybe you were looking at the following, which is a search for closed pull requests:
We're working on this already and trying our best to make it available on the next release.
This link might be what you're looking for: https://github.com/timescale/timescaledb/labels/pg15
Hi Chris! You are right I think haha. However I have run it for some time now and inserting 500k rows every day in production and have encountered no issues so far.
-------- Original Message -------- On 13 Jan 2023, 16:31, Chris Bandy wrote:
@.***(https://github.com/fboerman) I think maybe you were looking at the following, which shows only closed pull requests:
We're working on this already and trying our best to make it available on the next release.
This link might be what you're looking for: pg15
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Documentation appears to be partially updated now for Postgresql-15 support.
https://docs.timescale.com/install/latest/self-hosted/installation-linux/
notable this line: apt install timescaledb-2-postgresql-15
You’re right, TimescaleDB 2.9.2 indeed supports PostgreSQL 15, they just didn’t communicate it clearly. I’m at a conference with a few guys from Timescale right now, so I’m gonna talk to them about it.
and now there is an official timescaledb-ha docker image with postgis and pg 15, i was waiting for that
I've updated postgresql-timescaledb package in Alpine Linux v3.17 (latest-stable) to the latest version and rebuilt against postgresql15.
This currently still listed as apt install timescaledb-2-postgresql-14
still as of posting.
Release note for 2.10.0 says "Full PostgreSQL 15 support for all existing features".
However at Step 6 Install TimescaleDB: on https://docs.timescale.com/self-hosted/latest/install/installation-linux/ it says apt install timescaledb-2-postgresql-14
.
I found timescaledb-2-postgresql-15
package is in the repository.
$ apt show timescaledb-2-postgresql-15 2>/dev/null | head -2
Package: timescaledb-2-postgresql-15
Version: 2.11.0~ubuntu22.04
Is the Step 6 on https://docs.timescale.com/self-hosted/latest/install/installation-linux/ needed to be updated? Or is there something that timescaledb-2-postgresql-14 is better than timescaledb-2-postgresql-15 as of now?
How to upgrade TimescaleDB 2.5.1 with PostgreSQL 14 to PostgreSQL 15?
How to upgrade TimescaleDB 2.5.1 with PostgreSQL 14 to PostgreSQL 15?
It seems to have to have the TimescaleDB upgraded before PostgresQL upgrade