You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I execute ALTER EXTENSION timescaledb UPDATE TO "2.3.0"; it fails with:
postgres=# ALTER EXTENSION timescaledb UPDATE TO "2.3.0";
ERROR: extension "timescaledb" version mismatch: shared library version 2.3.0; SQL version 2.2.0
CONTEXT: parallel worker
To Reproduce
Steps to reproduce the behavior:
Create a dataset (I created 1 compressed hypertable, ~500M rows, ~10GB on disk)
Change postgresql.conf as such:
parallel_tuple_cost = 0.001
parallel_setup_cost = 1.0
force_parallel_mode = on
Restart the postgresql service
Execute ALTER EXTENSION timescaledb UPDATE TO "2.3.0";
See error
Expected behavior
Expected the upgrade to work.
Additional context
Setting max_parallel_workers = 0 in postgresql.conf fixes the issue.
For some reason, parallel execution of the upgrade process itself seems to trigger this bug.
A possible workaround could maybe be to inject SET max_parallel_workers = 0; in the upgrade scripts. E.g. in this specific case adding it as the first line of the file /usr/pgsql-13/share/extension/timescaledb--2.2.0--2.3.0.sql fixes the issue.
The text was updated successfully, but these errors were encountered:
Relevant system information:
=>
Timescale 2.3.0dnf
Describe the bug
When I execute
ALTER EXTENSION timescaledb UPDATE TO "2.3.0";
it fails with:To Reproduce
Steps to reproduce the behavior:
postgresql.conf
as such:ALTER EXTENSION timescaledb UPDATE TO "2.3.0";
Expected behavior
Expected the upgrade to work.
Additional context
Setting
max_parallel_workers = 0
inpostgresql.conf
fixes the issue.For some reason, parallel execution of the upgrade process itself seems to trigger this bug.
A possible workaround could maybe be to inject
SET max_parallel_workers = 0;
in the upgrade scripts. E.g. in this specific case adding it as the first line of the file/usr/pgsql-13/share/extension/timescaledb--2.2.0--2.3.0.sql
fixes the issue.The text was updated successfully, but these errors were encountered: