![]() ![]() usr/lib/postgresql/12/lib/timescaledb-tsl-2.3.0.so usr/lib/postgresql/12/lib/timescaledb-2.4.2.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.5.2.so usr/lib/postgresql/12/lib/timescaledb-2.3.1.so usr/lib/postgresql/12/lib/timescaledb-2.5.1.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.4.1.so usr/lib/postgresql/12/lib/timescaledb-2.2.1.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.1.0.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.5.0.so usr/lib/postgresql/12/lib/timescaledb-2.4.0.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.1.1.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.2.0.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.4.2.so usr/lib/postgresql/12/lib/timescaledb-2.2.0.so usr/lib/postgresql/12/lib/timescaledb-2.1.1.so usr/lib/postgresql/12/lib/timescaledb-1.7.5.so usr/lib/postgresql/12/lib/timescaledb-tsl-1.7.5.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.2.1.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.6.0.so usr/lib/postgresql/12/lib/timescaledb-2.5.0.so usr/lib/postgresql/12/lib/timescaledb-2.5.2.so usr/lib/postgresql/12/lib/timescaledb-2.3.0.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.3.1.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.4.0.so usr/lib/postgresql/12/lib/timescaledb-2.4.1.so usr/lib/postgresql/12/lib/timescaledb-2.1.0.so usr/lib/postgresql/12/lib/timescaledb-tsl-2.5.1.so LOG: TimescaleDB background worker launcher connected to shared catalogsĮRROR: could not access file "$libdir/timescaledb-2.6.0-dev": No such file or directory We use "make builder" to build ha images, but when run build image: How to add pg_stat_monitor to shared_preload_libraries config? ![]() I've also tried to updated configuration & set same values as in previous container, but that didn't change anything. Saving changes to: /home/postgres/pgdata/data/nf Recommendations based on 15.55 GB of available memory and 12 CPUs for PostgreSQL 13 Timescaledb.last_tuned_version = '0.12.0' In any case, thanks in advance for your help! timescaledb_toolkit/analytics not loading in timescale/timescaledb-ha:pg12.7-ts2.3.1-p1 But I'll see if I can reproduce it by switching off the watchtower container and performing a manual update. Unfortunately, I can't get any meaningful logs at the moment because I usually notice the image update too late. With timescaledb-docker-ha, however, the databases are now gone after every image update :-(Īm I missing something here? Do I have to make an additional setting for timescaledb-docker-ha? The databases I created remained intact even after an image update. This setup has always worked wonderfully with the original Timescaledb image. var/run/docker.sock:/var/run/docker.sock command: -interval 240 etc/localtime:/etc/localtime:ro environment:Ĭontainer_name: watchtower restart: always image: v2tec/watchtower networks: srv/dev-disk-by-uuid-someuuid/data/docker_data/timescale_ha:/var/lib/postgresql/data Container_name: timescale restart: always image: timescale/timescaledb-ha:pg14-latest networks: ![]()
0 Comments
Leave a Reply. |