Bug 2250354

Hey there team, 

I'm not sure if this one is deliberate or not (I can think of reasons you'd do it either way), but I can't see any documentation saying that this is the case so I'm raising as a bug. 

It looks like when packaging Timescale for Fedora we've got no mechanism to enable the Timescale license which unlocks about half of the features of the package, and is still 100% free (its essentially a non-compete with their hosting platform). 

To enable this license you need to flip a config switch in your postgresql.conf, which then loads some *waves hands* stuff from a lib that contains the non-apache features. This lib file does not exist in the Redhat rpm and so throws and error. I believe the problem also exists on other downstream distros and from my small about of clicking around has been in there since at least as far back as 29.

Reproducible: Always

Steps to Reproduce:
1.Install postgres + timescaledb on a fresh configuration using dnf
2.Open your postgres conf and add 'timescale' to your shared_preloaded_libraries config item
3.Add a new config item that looks like: timescaledb.license='timescale'
4.Restart your postgres: sudo service postgres restart
5.Run psql and connect to a db: sudo -p postgres psql
6.Enable the timescale extension: CREATE EXTENSION IF NOT EXISTS timescaledb;
Actual Results:  
It will throw the error:

"timed out waiting for connection: could not access file "$libdir/timescaledb-tsl-version-number": no such file or directory"

Expected Results:  
It should load the extension (exactly the same way it does if you don't have the license change config option enabled).

If we're being deliberate about not wanting to bundle this we should inform Timescale to update their docs, and include this note in our documentation so there can be a pathway for people who want to enable this feature.