database · inferred from evidence
Postgres
A relational database management system.
- Hasura UBI images force OpenSSL FIPS mode, breaking Postgres md5 password auth
On the UBI image variants of hasura/graphql-engine (images built on/after 2026-08-05, e.g. v2.45.8 and v2.50.x .ubi tags), connecting to a Postgres that requires md5 password auth failed with: psql: error: could not encrypt password (unsupp
- TimescaleDB Docker upgrade: could not access file "$libdir/timescaledb-X.Y.Z"
After upgrading the TimescaleDB Docker image, every query fails with `ERROR: could not access file "$libdir/timescaledb-1.4.0": No such file or directory`, even after `ALTER EXTENSION timescaledb UPDATE;` says the extension is up to date. T
- ValueError: Port could not be cast to integer value when connecting to Qovery Postgres from Python
Created a Postgres database in Qovery, copied the db_url from the dashboard, and used it with SQLAlchemy and the databases library in Python. Every connection attempt raised ValueError: Port could not be cast to integer value, pointing at p
- RudderStack server high CPU utilization even when idle starting with 1.17.0
After upgrading rudder-server from 1.16.3 to 1.17.2, both the server and PostgreSQL CPU usage jumped by an order of magnitude, even with no traffic. The reporter bisected the releases and found 1.17.0-rc1 was the first bad release. Another
- Neon "Error connecting to database: fetch failed" using drizzle and SST
I was connecting to Neon from an SST function using drizzle-orm/neon-http with the serverless driver, and every query died with Error connecting to database: fetch failed. The direct connection via npx drizzle-kit push worked fine, and the
- Tembo: CREATE EXTENSION pgcrypto fails — "extension \"pgcrypto\" is not available"
On Tembo, `CREATE EXTENSION pgcrypto;` fails with `ERROR: extension "pgcrypto" is not available` / `Detail: Could not open extension control file ... No such file or directory` / `Hint: The extension must first be installed on the system wh
- Supabase pgvector match function: operator does not exist (extensions schema)
Replicating the Clippy (Supabase docs) search on a personal Supabase project failed when calling the `match_page_sections` Postgres function with "operator does not exist". Reporters on self-hosted and hosted projects hit this when the `vec
- Logto fails to start: self signed certificate in certificate chain (managed Postgres)
Starting the Logto container against a DigitalOcean Managed Postgres database failed during initialization with Error: self signed certificate in certificate chain. DigitalOcean's managed databases present a certificate chain Node does not
- Chainguard wolfi-base postgres 16 client TLS connection failure openssl
A Postgres 16 client built on cgr.dev/chainguard/wolfi-base fails TLS connections to the server (e.g. Azure Database for PostgreSQL flexible server). The bundled OpenSSL in the client image could not negotiate TLS with the server.
- fly ssh console -C doesn't handle environment variables (PGPASSWORD)
I wanted to run a one-off command on my Fly postgres machine with env vars, like fly ssh console -a flaxidb -C "the postgres password env var psql -h [local address] -U postgres -c ...", but the -C argument mangled the environment variable
- Unable to update Elasticsearch mapping: elastic: Error 403 on Create Custom Attributes
Self-hosted Temporal 1.20.4 with AWS OpenSearch 2.5 and RDS Postgres. Creating a custom search attribute (`temporal operator search-attribute create --name CustomTest --type Keyword`) fails with: unable to update Elasticsearch mapping: elas
- How to get fixed egress IP addresses for Pipedream workflows
To query a Postgres database or any firewalled service from a Pipedream workflow, you need to whitelist the IPs the requests come from. Pipedream did not publish a list of egress IPs for regular workflows, which blocked corporate adoption w
- Langfuse docker compose fails on ARM: wrong-arch migrate binary, syntax error on ClickHouse migrations
Self-hosting Langfuse v3 via docker compose on an ARM64 Linux machine: the langfuse-web container crash-loops on ClickHouse migrations with `/usr/bin/migrate: line 1: syntax error: unexpected ")"` and `Applying clickhouse migrations failed`
- Flipt 1.9.0 Postgres dial tcp lookup postgres device or resource busy
Upgrading Flipt from 1.8.3 to 1.9.0 or 1.10.0 breaks Postgres connectivity in Kubernetes with: getting db driver for: postgres: dial tcp: lookup postgres.database.svc.cluster.local: device or resource busy. Versions 1.8.2 and 1.8.3 worked f
- ChromaDB DuplicateIDError on memgpt load (duplicate embedding IDs)
Running `memgpt load` with a large .jsonl dataset failed with "chromadb.errors.DuplicateIDError: Expected IDs to be unique, found duplicates of: ...". The dataset produced duplicate embedding IDs on load, and Chroma's `validate_ids` rejecte
- Meltano with Airflow fails: sqlite database file doesn't exist, do you need to create the database with...
After upgrading to Meltano 2.0, running Airflow failed with an error saying the sqlite database file didn't exist and asking whether to run `airflow db init`. The reporter had Airflow 1.10 configured and then tried 2.1, but the metadata DB
- EdgeDB restore fails with 'role already present in the schema' when the instance was bootstrapped with a...
A full EdgeDB dump would not restore with `SchemaError: role 'myuser' is already present in the schema`, even with --allow-non-empty --all. The root cause is that unlike Postgres, EdgeDB refuses to restore schema objects that already exist
- Flipt ERROR invalid input syntax for type integer OR_SEGMENT_OPERATOR SQLSTATE 22P02
Running Flipt with Helm and an on-premise Postgres database, everything works until you try to modify any entity: editing a variant flag or a segment constraint fails with ERROR: invalid input syntax for type integer: "OR_SEGMENT_OPERATOR"
- Airbyte MongoDB incremental sync fails repeatedly with "Saved offset is not valid"
Incremental syncs from MongoDB to Postgres kept failing with `java.lang.IllegalArgumentException: Saved offset is not valid`. The sync would then retry from a full refresh, which was expensive on a large collection. A community member trace
- PGRST303 "JWT issued at future" on REST requests using the new sb_secret_ key
After moving to the new non-JWT sb_secret_ key format, REST calls authenticated with the service-role key intermittently return 401 with proxy_status PostgREST and error PGRST303 ("JWT issued at future"). The odd part: the client only ever