database · inferred from evidence
Postgres
A relational database management system.
- 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
- 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
- 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
- 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
- Log bloat with "has a collation version mismatch" warnings on template1 after Postgres 17 upgrade
After the managed Postgres 17 upgrade, the database logs are continuously flooded with warnings: database "template1" has a collation version mismatch (error code 01000), recurring roughly every 60 seconds and burying everything else in the
- Error opening a TLS connection: self-signed certificate in certificate chain (Prisma 7, code P1011)
After upgrading from Prisma 6 to Prisma 7, every query crashes with "Error opening a TLS connection: self-signed certificate in certificate chain" (PrismaClientKnownRequestError, code P1011). The app itself returns 200 but dies at the first