PostgreSQL backfills are slow and risky
Data engineering2 posts from 2 people2d active+00 posts in the last 7 days, 1 the 7 days before (fading)Unverified
Posts per day
The posts behind it
2, newest first[BUG] Trace analytics migration 75868b020152 is O(n²) on PostgreSQL: spans keyset pagination can't use the primary key index> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...mlflow/mlflow · MatasVS5 repliesOpen ↗Production database unavailable after disk exhaustion and disk expansion...reflected by the new 8 GB allocation; - Supavisor/database authentication services are unable to reach the backend; - another platform-side service requires intervention after the original disk-full crash. Once connectivity is restored, we will perform read-only integrity...supabase/supabase · esolanOpen ↗
Companies and products named
About this problem
Evidence
2 posts from 2 people in 2 places, about 2 a week over 7 days. Mostly on supabase/supabase, mlflow/mlflow. Tools named alongside: Supabase, MLflow, SQLite, SQL Server.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "backfills" rule about PostgreSQL. First post Oct 7, 2026, latest Oct 13, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
Other PostgreSQL problems
PostgreSQL upgrades break working setupsPostgreSQL error messages are crypticPostgreSQL queries run too slowly and are hard to tuneTrouble with PostgreSQL databasePostgreSQL permissions are confusing and error-pronePostgreSQL connectors and syncs are fragilePostgreSQL feels slow and laggyPostgreSQL outages and slowdowns disrupt workTrouble with PostgreSQL triggerPostgreSQL rate limits and usage caps block workRAG on PostgreSQL returns irrelevant or missing contextMigrating to or off PostgreSQL is slow and risky
History
steady to fading
PostgreSQL backfills are slow and risky (2 posts)