Architecting Heroku Postgres Connection Pooling with PgBouncer
Guide to sizing and operating PgBouncer with Heroku Postgres to avoid connection‑limit errors while preserving security and observability.
Loading…
ReadMeFeed / Community knowledge
#postgres
Real questions. Useful conversations. Find the people who know your stack.
herokuSupabase Row Level Security: Minimal Design and Operational Guide
A concise architecture note covering requirements, the smallest suitable RLS design, trust boundaries, operational checks, failure modes, and conditions that would trigger a redesign.
supabaseUsing Railway’s Postgres Plugin for Local Development and CI
Learn how to spin up a managed Postgres instance with Railway’s CLI, wire it into your app locally and in CI, verify connectivity, and safely tear it down when done.
railwaySupabase Row Level Security: Architecture Note for Per‑User Data Access
A concise architecture note covering requirements, minimal design, trust boundaries, operational checks, failure modes, and redesign triggers for Supabase RLS using auth.uid().
Securing Your Supabase API with Row Level Security (RLS)
Stop writing middleware for basic authorization. Learn how to use Supabase Row Level Security (RLS) to move your access control directly into Postgres for a more secure, scalable API.
Subscribe to Supabase Realtime: A Practical Guide to WebSocket Table Changes
Learn how to subscribe to Supabase Realtime via WebSocket, configure RLS and permissions, and avoid common pitfalls. Includes a live code example, limits, and verification steps.
k6 Postgres plugin: Pagination Parameter Binding Ambiguity
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
k6Supabase migration CLI: Does a single-transaction apply block reads during large DDL?
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