Closed Vonng closed 3 years ago
@Vonng can you please run and show the output of:
SELECT * from pg_settings where name ~ 'timescaledb.license';
or
SHOW timescaledb.license
?
postgres@meta:5432/a=# select * from pg_settings WHERE name ~ 'timescaledb.license';
-[ RECORD 1 ]---+--------------------------------------
name | timescaledb.license
setting | apache
unit | NULL
category | Customized Options
short_desc | TimescaleDB license type
extra_desc | Determines which features are enabled
context | superuser
vartype | string
source | default
min_val | NULL
max_val | NULL
enumvals | NULL
boot_val | apache
reset_val | apache
sourcefile | NULL
sourceline | NULL
pending_restart | f
Besides. CentOS 7.8.2003 x86_64 & timescaledb 2.1 behave the same (apache
by default).
@Vonng can you please run and show the output of:
SELECT * from pg_settings where name ~ 'timescaledb.license';
or
SHOW timescaledb.license
?
I believe this arises because @Vonng installed TimescaleDB via the Postgres GDG repositories, rather than Timescale repositories.
Installation method: yum (via official pgdg13 repo)
Unfortunately, there's a naming conflict:
timescaledb
to mean the Community edition, and timescaledb-oss
to mean the Apache2 edition. timescaledb
for the Apache2 edition, while they ship timescaledb-tsl
as the Community edition. If you'd like to install TimescaleDB via our builds, we recommend following these instructions:
Thanks for your reply. It do solves the problem (install via timescale_timescaledb
repo).
The rpm in pgdg
repo has a confusing name, and I could not find timescaledb-tsl
or any timescale
licensed version in it. It would be great if it keeps up with your repo. 😆
I believe this arises because @Vonng installed TimescaleDB via the Postgres GDG repositories, rather than Timescale repositories.
Installation method: yum (via official pgdg13 repo)
Unfortunately, there's a naming conflict:
- Timescale uses
timescaledb
to mean the Community edition, andtimescaledb-oss
to mean the Apache2 edition.- Postgres GDG uses
timescaledb
for the Apache2 edition, while they shiptimescaledb-tsl
as the Community edition.If you'd like to install TimescaleDB via our builds, we recommend following these instructions:
@Vonng I agree the naming is confusing! I wish I had an obvious fix =)
https://twitter.com/michaelfreedman/status/1397641632552570880
Relevant system information:
Describe the bug
The default value for
timescaledb.license
isapache
. While as the doc says the default value is 'timescale'Which means the default installation & setup will fail on some 'timescale' license features. Leads to errors such as
function xxx is not supported under the current "apache" license
To Reproduce Steps to reproduce the behavior:
Expected behavior
Actual behavior
Screenshots
Additional context