Timescaledb: PostgreSQL 12 support

Created on 26 Sep 2019 · 41Comments · Source: timescale/timescaledb

Hi,
Timescaledb 1.4.2 does not compile against v12. Can you please release a new version? v12 is out next week.

Regards, Devrim

enhancement

Source

devrimgunduz

👍37

Most helpful comment

Hey folks, just flagging that our PR was submitted against master for PG12 support, and it should be merged soon.

69 commits and 282 files changed!

https://github.com/timescale/timescaledb/pull/1807

cc: @devrimgunduz

mfreed on 14 Apr 2020

🎉20 ❤8 🚀7 👍2

All 41 comments

We are currently working on this, and will be in a better position to set timelines once we get a little further into the process, I will update this thread when we are ready to set timeline expectations.

bboule on 26 Sep 2019

👍19

Thanks!

devrimgunduz on 27 Sep 2019

👍3

On Windows 10 64 bit -- I note that TimescaleDB also does not work with PostreSQL version 11.5.2 (well not straight out of the box) but worked fine with 11.0.3. The timescale extension DLL does not load as it had dependencies on the OpenSSL DLL's ssleay32.dll and libeay32.dll which were present in earlier PostgreSQL version but in 11.5 were replaced with the newer libcrypt/libssl. As a result two DLL's required by timescale were missing and as a workaround one could grab compatible versions and place them in the lib folder once you had figured out what was wrong. How horrible is that? Secondly for version 12 we find PostGIS is missing in stack builder so if you want both TimescaleDB and PostGIS then best to forget version 12 of PostgreSQL until that gets resolved. It seems right now the only available installer for 11 is 11.5 (older versions are not available on the EDB site for some unknown reason) so it seems you have to use that one and deal with those missing dlls. Is TimescaleDB ever going to be available in stack builder? Would be nice if it could be!

bluespidernav on 15 Oct 2019

I see milestone 1.6 was added to this issue - would you have any rough estimate when we could expect this release?

fvannee on 22 Oct 2019

@fvannee we do not yet we are still in the planning stages but we will be sure to update this thread as soon as the timeline becomes clear

bboule on 22 Oct 2019

👍3

@bboule ok thank you for the update. let me know if a preliminary version would need to be tested at some point. i'd be happy to help.

fvannee on 22 Oct 2019

Hello!
Usually after how many months support for the new version of postgresql is added?

nailgilaziev on 26 Nov 2019

And in the meantime PostgreSQL 12.1 is out: https://www.postgresql.org/docs/12/release-12-1.html

extesy on 26 Nov 2019

Minor versions doesn't change the API/SPI starting from PostgreSQL 10 - see https://www.postgresql.org/support/versioning/

jesperpedersen on 26 Nov 2019

👍1

Hey @bboule

We are currently working on this, and will be in a better position to set timelines once we get a little further into the process, I will update this thread when we are ready to set timeline expectations.

Just wondering how your team is progressing with this? Any updates?

Regards,
Damien.

damoclark on 5 Dec 2019

We are currently working on this, and will be in a better position to set timelines once we get a little further into the process, I will update this thread when we are ready to set timeline expectations.

Just wondering how your team is progressing with this? Any updates?

Current plan is to release at the beginning of next year as part of 1.7 release. I guess it will be more clear after all the holidays.

k-rus on 5 Dec 2019

👍8 😕1

Assuming support will include 12.1+ ...by beginning of next year, is that Jan? Feb? or by end of Q1? Thanks!

Best,
Chris

apcmaff on 12 Dec 2019

👍5

The current plan of release is end-of-Jan beginning-of-Feb

cevian on 19 Dec 2019

👍9

Thanks for the update @cevian

fvannee on 19 Dec 2019

👍1

@cevian Are there any specific tasks that the community can do?

webnard on 15 Jan 2020

about the current progress?

zplzpl on 30 Jan 2020

Please note: We decided to delete one comment posted to this issue within the past 24 hours (and some follow-up responses). This is a first for us, to my knowledge.

The comment, made by somebody who has no association with Timescale, was wildly inappropriate and divisive. This type of sentiment has no place in our community, and we will not accept it.

As a side note to the broader discussion, the team _is_ hard at work getting PostgreSQL 12 support out the door, and it will be in our next release, v1.7. You can follow along with the large PR here (currently at 55 commits).

mfreed on 3 Feb 2020

👍8 🚀2

TimescaleDB Team,
We are looking for TimescaleDB version compatible to PostgreSQL-12. As mentioned before TimescaleDB for PG12 will be ready around Feb 2020. If beta version or version ready please help to share.
If NOT ready let us know availability date. If available by Feb 2020 will be great.
Waiting for response.

Regards,
Vivek

vivekanandsh on 3 Feb 2020

👎1

@vivekanandsh We are currently tracking to a March release date.

mfreed on 3 Feb 2020

@mfreed What is Timescale's stance in general on supporting new versions of Postgres?
I love using TimescaleDb, but I found it usually causes delays in adopting newer Postgres versions. For example, PG11 was also only properly supported several months after it was released (version 1.2.0, end of January).
I understand it's quite a large undertaking to adopt all the changes in a new Postgres release, which is something that takes time. However, some other (also rather large and complex) extensions are often quite a bit faster in supporting new versions. Either they try to keep up-to-date with Postgres master during development, or they start their work to support new versions already when PG brings out the first early Beta release. I get the idea, but please correct me if I'm wrong, that Timescale's policy is to start working on support for a new version only after the final release of Postgres is released.

fvannee on 11 Feb 2020

👍2

@fvannee We don't have a hard-and-fast rule here, and scheduling engineering resources early on PG12 was balanced against other development priorities.

In this case, the main things we focused on in 2019, rather than prioritizing PG12, was multi-node, compression, and continuous aggregates. I understand that folks would have liked PG12 support out earlier, but looking back, I'm not sure we would have made different decisions at the time. I also think those capabilities are really valued by the community.

We'll try to give PG13 a little more priority up front, but again it's always a balancing act.

I would also say that if the community would like to contribute by helping us track PG13 master more closely, this is really some place that we'd very much welcome the help, and might be a "right-sized" project for some external contributors? Thoughts?

mfreed on 12 Feb 2020

👍8

mfreed ,
I love using TimeScaleDB. Thanks for your engineering effort. I do agree and good if timescaledb latest version released after ( lesser time gap) major versions of PostgreSQL. As requested before i held my release to production as i am waiting for TimeScaleDB version compatible to PG12. As you mentioned tentative planned date in March 2020. Good if get TimeScaleDB beta for PG12 by first/second week of March 2020.

vivekanandsh on 12 Feb 2020

👍3 👎1

For folks that are interested in possibly contributing to the continuous PG13 integration, please shoot me at email? mike (at) timescale com

mfreed on 17 Feb 2020

👍1

@vivekanandsh We are currently tracking to a March release date.

Is this still the plan?

gajus on 27 Feb 2020

Yes at this point we are still tracking to March release.

bboule on 27 Feb 2020

👍4

@bbouble
Thanks we are waiting for March release for PG12. Any beta release available help share. We will verify for PG12.

vivekanandsh on 28 Feb 2020

Hi,

I have multiple cluster version of postgresql installed
Any idea how to install timescaledb for specific version?

/usr/lib/postgresql/12/bin/postgres
/usr/lib/postgresql/10/bin/postgres
/usr/lib/postgresql/11/bin/postgres
/usr/lib/postgresql/9.5/bin/postgres

Error:

sudo timescaledb-tune
exit: unknown major PG version: PostgreSQL 12.2 (Ubuntu 12.2-2.pgdg16.04+1)

tienlx93 on 12 Mar 2020

@mfreed ,
Any update on timescaledb for PpstgresSQL 12 version. We are waiting for this release.

vivekanandsh on 16 Mar 2020

👎8 👍1

TimescalDB Team,
Support for PostgresSQL 12 version is till tracking to March release ?

vivekanandsh on 18 Mar 2020

👎9 👍1

At this point I expect PG13 support before we get PG12 support :)

On Sun, Mar 29, 2020 at 5:19 PM Ali Roaidi notifications@github.com wrote:

I hope you guys are making progress :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/timescale/timescaledb/issues/1456#issuecomment-605703297,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACI4XRXUG4HUQFYP77C6IU3RJ63NTANCNFSM4I24RIZQ
.

brolly759 on 30 Mar 2020

👎7

TimeScaleDB Team,

Any update on release plan for PostgresSQL 12 version. Earlier planned for March 2020. Please let us know urgently. If postponed/delayed also please update.

vivekanandsh on 30 Mar 2020

👎10

Guys instead of spamming everyone's email accounts, why don't you just wait for an update? I'm sure the TimescaleDB team will update when they have something to share.

Also, this is an open source project so if their pace is not fast enough for you, you can always create a PR yourselves.

pehlert on 30 Mar 2020

👍10

We're currently doing internal testing of TimescaleDB with PostgreSQL 12 support. PostgreSQL 12 turned out to be a bigger task than anticipated due to a large number of internal changes in PostgreSQL, in particular related to partitioning and the introduction of table access methods.

We should have a further update on this in the very near future.

erimatnor on 30 Mar 2020

👍13

@brolly759, @vivekanandsh, @pehlert According to the latest newsletter, PostgreSQL 12 will be supported by TimescaleDB 1.7. See also https://github.com/timescale/timescaledb/milestone/39.