-
Notifications
You must be signed in to change notification settings - Fork 883
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to timescaleDB 2.0 failed ("shared library version mismatch") #2795
Comments
I had the same issue, you have to (temporarily) set max_parallel_workers to 0. After upgrade you can revert it back to original value. |
It's ok now. |
So you were getting that error about the SELECT when you try to run Thanks! |
Yes, first command was always 'ALTER EXTENSION timescaledb UPDATE;' in new psql session connect with 'psql -X zabbix'. change parallel_max_worker = 0 in file |
I get this issue while using docker in a DB that has never seen Zabbix and has no other services running. Details edit:
Have not tried a full reproduction chain, but I imagine it would follow a path of something like: installation, enabling compression, letting that run, then attempting the upgrade. |
Had same issue and this solved it, thanks. |
This issue also solved it for me, but the symptoms of upgrading while max_parallel_workers > 0 were very very different. For me the upgrade process ran for 24-36 hours and then failed with no clue why. When I set max_parallel_workers = 0 in the config file (suggested by Mike, thanks!), then the same update took less than a minute and completed successfully. I strongly recommend that you suggest in your documentation that people upgrading timescale set max_parallel_workers = 0 before doing the upgrade! |
Same issue on TimescaleDB v2.3.0 and changing max_parallel_workers to 0 helped! |
Probably the same issue #3286 |
To update from timescaledb v.2.2.1 to v.2.3.0 I need to change this parameters and it work.
At first I change only max_parallel_workers but got error , out of shared memory then I change max_locks_per_transaction to 1024. ALTER extension timescaledb update now work. |
I'm not the best postgres expert, this is what I did to try to migrate timescaledev/promscale-extension 0.1.1->0.1.2-2.3.0-pg12, promscale:0.1.2 -> 0.4.1. I ended up only upgrading to promscale:0.3.0. If someone has any better idea how to do this... (Using docker) docker stop promscale-connector
docker restart promscale-db
docker start promscale-connector
Going back to promscale:0.3.0
|
I also needed this to make the update work. @mfundul I think your commit will fix the |
Having this issue. I needed to go from 2.13.0 to 2.12.2 to restore a backup. Then I can't upgrade back to 2.13.0 Except the error message is different. So maybe I should log a new issue?
|
Hello @jflambert, Thanks for bringing this to our attention. This seems to be the same issue as reported in #6496. Please check if the workaround provided in this issue also fixes the problem in your environment. |
I'm sorry I made you reopen this issue. It's definitely the other one. Looking forward to 2.13.1 |
Relevant system information:
postgres --version
): psql (PostgreSQL) 12.5\dx
inpsql
): 1.7.4We use patroni for clustering postgres with 2 members on learder and one replica
patroni 2.0.1
Describe the bug
When we try to upgrade, it's failed with this message:
ERROR: extension "timescaledb" version mismatch: shared library version 2.0.0; SQL version 1.7.4
CONTEXT: parallel worker
SQL statement "SELECT sum(_ts_meta_count), count(*) FROM _timescaledb_internal.compress_hyper_8_489_chunk"
PL/pgSQL function inline_code_block line 21 at EXECUTE
To Reproduce
Steps to reproduce the behavior:
1- Install timescaledb RPM for 2.0 yum install timescaledb-2-postgresql-12.x86_64
2 - psql -X zabbix
3- ALTER EXTENSION timescaledb UPDATE;
4 - ERROR: extension "timescaledb" version mismatch: shared library version 2.0.0; SQL version 1.7.4
CONTEXT: parallel worker
SQL statement "SELECT sum(_ts_meta_count), count(*) FROM _timescaledb_internal.compress_hyper_8_489_chunk"
PL/pgSQL function inline_code_block line 21 at EXECUTE
Thanks in advance for your help
The text was updated successfully, but these errors were encountered: