I was moving a postgresql database cluster to another server and did what I thought was the simplest way, to copy the data files and start up a new server of the same version (in my case, v. 14, this was the first step in a server upgrade, the old server was on centos7, the new one is rockylinux 9). This worked well for all the databases, except for the one that was using timescaledb where the tables are unavailable even though I have installed timescaledb also on the new server. (I also have some databases using postGIS heavily, those are working just fine after the move). After starting the up the new server, I have had to manually run a "Create extention timescaledb", that seems to work and \dx shows the extension, but the data are not accessible. Any tips on what to do?
1 Answer 1
It turned out that on the new installation, I had installed timescale with apache license. Just switched to the community licence version and everything worked fine.
This was on rocky linux 9. At first I installed timescaledb from the postgres, pgdg, repo. I had to also add the timescaledb repo to get access to the community licence version.