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
Attempting to update from 1.5.1 to 1.6.0 failed with error message: ERROR: attempt to redefine parameter "timescaledb_toolkit_acknowledge_auto_drop"
To Reproduce
Steps to reproduce the behavior:
docker run -d --name tsdb -p 5432:5432 -e POSTGRES_PASSWORD=password timescale/timescaledb-ha:pg14.2-ts2.6.1-latest
docker exec -it tsdb psql -U postgres
CREATE EXTENSION timescaledb_toolkit VERSION "1.5.1";
\dx timescaledb_toolkit;
ALTER EXTENSION timescaledb_toolkit UPDATE; should produce the aforementioned error. More importantly, the toolkit version stays at 1.5.1, not 1.6.0.
Expected behavior
timescaledb_toolkit extension should be updated to "1.6.0"
Actual behavior
timescaledb_toolkit extension stays at "1.5.1".
Workaround
Start a new psql session and run ALTER EXTENSION timescaledb_toolkit UPDATE;, the extension may be updated correctly. I've seen this happening twice to me.
The text was updated successfully, but these errors were encountered:
Relevant system information:
Describe the bug
Attempting to update from 1.5.1 to 1.6.0 failed with error message:
ERROR: attempt to redefine parameter "timescaledb_toolkit_acknowledge_auto_drop"
To Reproduce
Steps to reproduce the behavior:
docker run -d --name tsdb -p 5432:5432 -e POSTGRES_PASSWORD=password timescale/timescaledb-ha:pg14.2-ts2.6.1-latest
docker exec -it tsdb psql -U postgres
CREATE EXTENSION timescaledb_toolkit VERSION "1.5.1";
\dx timescaledb_toolkit;
ALTER EXTENSION timescaledb_toolkit UPDATE;
should produce the aforementioned error. More importantly, the toolkit version stays at 1.5.1, not 1.6.0.Expected behavior
timescaledb_toolkit extension should be updated to "1.6.0"
Actual behavior
timescaledb_toolkit extension stays at "1.5.1".
Workaround
Start a new
psql
session and runALTER EXTENSION timescaledb_toolkit UPDATE;
, the extension may be updated correctly. I've seen this happening twice to me.The text was updated successfully, but these errors were encountered: