Problemsby GlyphTrouble with PostgreSQL flow
3 posts from 3 people3d activeSteady, +1 this week
Posts per day
The posts behind it
Flow run stored with a deeply nested, lone-surrogate or NaN-label value makes `/flow_runs/filter` return 500 for every client
### Bug summary The server stores some values that it can't serialize when reading them back. After that, every list request whose page includes the row returns 500 until the row is deleted. This is the same failure as #15031, but caused by different inputs, and the #15031 fix...
schedule trigger not triggering the flow
## Describe the problem/error/question most of schedule triggered flow had been palatized during September 14 -19, then again during September 26 - 30. No idea why and how we can prevent or at least detect the execution status actively? ## What is the error message (if any)?...
PostgreSQL /flow_runs/filter times out for state-filtered START_TIME_ASC queries on large flow_run tables
### Bug summary We observed `POST /flow_runs/filter` returning HTTP 500 for the following query against a self-hosted Prefect server using PostgreSQL: Our `flow_run` table contained approximately 6.35 million rows (26 GB), including approximately 27,000 `RUNNING` rows. Prefect...
Companies and products named
About this problem
Evidence
3 posts from 3 people in 2 places, about 1 a week over 43 days. Mostly on PrefectHQ/prefect, n8n-io/n8n. Tools named alongside: Prefect, Docker, n8n, SQLite.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about PostgreSQL with no known issue, sharing the word "flow". First post Sep 15, 2026, latest Oct 27, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other PostgreSQL problems
PostgreSQL users keep filing bugs
Top post: "Postgres row-level security leaks across tenants when using a pooled connection", one of 41 posts from 39 people on GitHub issues, Stack Overflow, Reddit.
PostgreSQL upgrades break working setups
12 posts from 11 people on GitHub issues, Stack Overflow, Reddit.
PostgreSQL queries run too slowly and are hard to tune
8 posts from 8 people on Reddit, Stack Overflow, GitHub issues.
Trouble with PostgreSQL database
Top post: "Canonicalising unit names from a flat file in a normalised database structure", one of 6 posts from 6 people on GitHub issues, Stack Overflow.
PostgreSQL error messages are cryptic
6 posts from 6 people on GitHub issues, Stack Overflow.
PostgreSQL permissions are confusing and error-prone
5 posts from 5 people on GitHub issues, Hacker News.
PostgreSQL feels slow and laggy
4 posts from 4 people on Mastodon, Reddit, GitHub issues.
PostgreSQL connectors and syncs are fragile
4 posts from 4 people on GitHub issues, Hacker News.
Trouble with PostgreSQL server
Top post: "SQL Server to PostgreSQL sync missing some records", one of 3 posts from 3 people on Reddit, GitHub issues, Stack Overflow.
PostgreSQL hits connection, locking and scaling limits
3 posts from 3 people on Reddit, GitHub issues, Stack Overflow.
Trouble with PostgreSQL shared
Top post: "The same UPDATE intermittently needs far more shared buffers for about a minute", one of 3 posts from 3 people on GitHub issues, Stack Overflow.
Trouble with PostgreSQL jsonb
Top post: "Should semi-structured product attributes (secondary images, specs) be stored as JSONB or normalized tables?", one of 3 posts from 3 people on Stack Overflow.
History