TimescaleDB - Community v Apache

[anton-schieber]

Hey,

Curious if you would consider supporting different versions: https://docs.tigerdata.com/about/latest/timescaledb-editions/

For example, if my table is set up to use compression (not supported in apache version) it would error out and fail to complete migration

The current output looks something like this:

SELECT create_hypertable('orders', 'timestamp');
SELECT set_chunk_time_interval(orders', INTERVAL '7 day');
ALTER TABLE orders SET (timescaledb.compress = true);
SET timescaledb.enable_chunk_skipping = 'ON';
SELECT enable_chunk_skipping('orders', 'device_id');

Instead could it have something like which will allow it to always pass the migration regardless of which version/ext of timescaledb used

DO $$
DECLARE
    license TEXT;
BEGIN
    SELECT current_setting('timescaledb.license', true) INTO license;

    -- Create hypertable (works for all licenses)
    PERFORM create_hypertable('orders', 'timestamp', if_not_exists => TRUE);

    -- Only run enterprise features if license is not 'apache'
    IF license IS DISTINCT FROM 'apache' THEN
        PERFORM set_chunk_time_interval('orders', INTERVAL '7 day');
        EXECUTE 'ALTER TABLE orders SET (timescaledb.compress = true)';
        PERFORM enable_chunk_skipping('orders', 'device_id');
    ELSE
        RAISE NOTICE 'Skipping enterprise-only features (compression, chunk skipping)';
    END IF;
END $$;

[sebastian-ederer]

Yes, that's a great idea. Currently I am working on implementing support for continuous aggregates and next week I'll be busy with a new project in work so I got no time for this currently.
However, feel free to make a PR if you don't want to wait that long. :)

You just might want to wait until I've merged the new continuous aggregat feature as I made some architectual changes to keep the project organized.
I'll probably merge it this week.

[sebastian-ederer]

@anton-schieber I just merged the new feature. So now you can safely fork the project and create a PR without getting too much problems with merge conflicts later on if you want to. :)

[anton-schieber]

anton-schieber#1

Implemented here, dependant on my other PR merging though

EDIT: need to update unit tests