timescaledb

问题 If I create the pg_cron extension in a docker-entrypoint-initdb.d/init.sql file, the docker image fails to run and docker logs <id> just says "No such container." Here's the relevant .sql snippet: CREATE DATABASE my_database; \c my_database; CREATE EXTENSION IF NOT EXISTS postgis CASCADE; CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE; CREATE EXTENSION IF NOT EXISTS pg_cron CASCADE; However, if I create the pg_cron extension after the docker run command completes (i.e. remove the last

问题 If I create the pg_cron extension in a docker-entrypoint-initdb.d/init.sql file, the docker image fails to run and docker logs <id> just says "No such container." Here's the relevant .sql snippet: CREATE DATABASE my_database; \c my_database; CREATE EXTENSION IF NOT EXISTS postgis CASCADE; CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE; CREATE EXTENSION IF NOT EXISTS pg_cron CASCADE; However, if I create the pg_cron extension after the docker run command completes (i.e. remove the last

问题 As specified in the official docs I added the Timescale PPA repository to apt . I then installed it via sudo apt install timescaledb-postgresql-9.6 . All was working fine. With a recent run of sudo apt upgrade the timescale package got updated from 0.8.0~ubuntu16.04 to 0.9.1~ubuntu16.04 . When running my Python script for inserting some new data I now get the following error (and nothing is being inserted): 2018-04-12 09:42:06,279 ERROR Postgres: could not access file "timescaledb-0.8.0": No

问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

问题 I have a Timescaledb server running as StatefulSet in AKS. It appears when I delete and recreate timescaledb pod, the changes are lost even though the pod is associated to the initially associated PV (persistent volume). Any help is appreciated. Below is the PV, PVC config of statefulset extracted by running kubectl get statefulset timescaledb -o yaml template: metadata: creationTimestamp: null labels: app: timescaledb spec: containers: - args: - -c - config_file=/etc/postgresql/postgresql

问题 I have a Rails 4.2.11.1 application that I am trying to use with a TimescaleDB database. I've solved the majority of the issues already (using the composite_primary_keys gem to get around Timescale's restriction that unique indexes should always include the table's timestamp column). This has my application fully functional, but my test suite fails whenever I try to write to the Timescale table, with the following error: PG::FeatureNotSupported: ERROR: invalid INSERT on the root table of

问题 I'm stuck using TimescaleDB in Rails - everything works fine in development, but in my test suite I cannot insert any data. What I tried A) Use SQL schema dump This causes the original error message I saw. It does create parts of the schema for TimescaleDB but not all of it. I have a hypertable but it's not working properly B) Use Ruby schema dump This lets me insert into my table but it's not a hypertable at all - the ruby syntax looses everything related to TimescaleDB and hypertables. C)