ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal: Identify whether the platform should provide a proactive compatibility check or require explicit user confirmation before performing a major version upgrade of Heroku Postgres that could break existing client‑library connections. Constraints: Heroku Postgres upgrades via `heroku pg:upgrade` change the server version while preserving data, but the platf
k6 – k6-postgres Plugin: Pagination Parameter Interaction The k6 Postgres plugin exposes a query method that accepts a raw SQL string and optional parameters. While pagination is typically achieved by embedding LIMIT and OFFSET clauses, the plugin documentation does not specify how query parameters interact with these clauses. Specifically, it is unclear whe
Supabase migration CLI and transaction scope The Supabase CLI’s supabase migration apply runs all SQL statements in a single transaction by default. When a migration includes large DDL changes—such as adding an index to a table with millions of rows—this transaction can acquire an exclusive lock on the target table. The lock may prevent concurrent SELECTs, l
heroku
k6
supabase