database · inferred from evidence
Postgres
A relational database management system.
- Hasura UBI images force OpenSSL FIPS mode, breaking Postgres md5 password auth
This was a Hasura image bug, fixed upstream (maintainer hgiasac confirmed "Fixed"). Pull a rebuilt .ubi image newer than the fix, or use the .ubuntu variant which was never affected. There is no per-container workaround worth keeping: unset
- TimescaleDB Docker upgrade: could not access file "$libdir/timescaledb-X.Y.Z"
Run `ALTER EXTENSION timescaledb UPDATE;` in every database where TimescaleDB is installed, including the `postgres` database, which people often forget (sometimes even `template0` needs it). If you are jumping several versions at once, do
- RudderStack server high CPU utilization even when idle starting with 1.17.0
Versions 1.17.0 through 1.17.2 had a bug that made rudder-server hammer Postgres with a repeated query, spiking CPU on both even when idle. Fix: upgrade rudder-server to v1.17.3 or later, which contains the fix for the query loop. 1.16.3 wa
- Supabase pgvector match function: operator does not exist (extensions schema)
Two things to check. First, pgvector requires Supabase Postgres 15.1.0.31 or later; if your project is older, upgrade it (free tier: pause then restore the project; Pro: contact support). Second, install/enable the vector extension in the `
- Tembo: CREATE EXTENSION pgcrypto fails — "extension \"pgcrypto\" is not available"
Install it via the Tembo UI first: Extensions → Explore → search for pgcrypto → Install Extension, then Enable Extension. Install Extension pulls the extension from pgt.dev into your Postgres cluster; Enable Extension then runs CREATE EXTEN
- fly ssh console -C doesn't handle environment variables (PGPASSWORD)
The -C flag was passing the command in a way that dropped the environment variable assignment. The fix was on Fly's side: an updated tool that handles exec with env properly. For existing apps you need to pick it up by running fly deploy or
- Flipt 1.9.0 Postgres dial tcp lookup postgres device or resource busy
This was a Flipt regression fixed in v1.9.1 and v1.10.1, upgrade to either of those patch releases and the Postgres connection works again. The reporter confirmed v1.9.1 fixed it in both local Rancher Desktop and GCP clusters. If you must s
- Unable to update Elasticsearch mapping: elastic: Error 403 on Create Custom Attributes
The cluster was in dual visibility mode: both visibilityStore (pointing at Postgres) and advancedVisibilityStore (pointing at OpenSearch) were set. Adding search attributes is not supported in dual visibility mode, which exists only to supp
- ChromaDB DuplicateIDError on memgpt load (duplicate embedding IDs)
This was a Flipt regression fixed in v1.9.1 and v1.10.1, upgrade to either of those patch releases and the Postgres connection works again. The reporter confirmed v1.9.1 fixed it in both local Rancher Desktop and GCP clusters. If you must s
- Flipt ERROR invalid input syntax for type integer OR_SEGMENT_OPERATOR SQLSTATE 22P02
This was a Flipt bug in the Postgres write path for segment operators, fixed in release 1.58.2. The reporter confirmed 1.58.2 resolved it. Upgrade to 1.58.2 or later; a nightly build containing the fix was also available while the release w
- PGRST303 "JWT issued at future" on REST requests using the new sb_secret_ key
This is transient clock drift between Supabase's own backend services, not a client-side bug. With the new opaque key format, the gateway exchanges your sb_secret_ key for a short-lived internal token minted with the gateway node's own cloc
- Log bloat with "has a collation version mismatch" warnings on template1 after Postgres 17 upgrade
Fix your own databases first with ALTER DATABASE postgres REFRESH COLLATION VERSION; (run once per user database) — that clears the mismatch everywhere except the template databases. template1 requires superuser, so you cannot self-serve: i