ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #postgresql
We run Ory Hydra with a PostgreSQL backend and are capacity-planning for workloads that issue many simultaneous calls to the POST /oauth2/revoke endpoint, for example during mass logout or incident-driven token cleanup. Our concern is latency that appears only under concurrency, not in single-request benchmarks. From community discussions and Hydra's own doc
Goal: Ensure a Yii 2.x migration can apply a CREATE INDEX CONCURRENTLY statement on a live PostgreSQL database without causing the migration to fail or leaving the database in an inconsistent state after a rollback. Constraint: Yii migrations wrap each step in a transaction by default, but PostgreSQL rejects CREATE INDEX CONCURRENTLY when executed inside a t
Goal: Assess whether Ecto can guarantee that a migration’s down function restores the database to its pre‑migration state after a schema change Ecto runs each migration inside a single transaction, but the generated down callback does not automatically undo data modifications that occur before the schema alteration. Certain schema operations—such as changing
Goal Determine whether a standby server that was initially set up with wal_level=replica must be restarted, reinitialized, or simply have its wal_level parameter changed and reloaded after the primary’s wal_level is switched to logical during a pg_upgrade to PostgreSQL 14, in order to maintain logical replication compatibility. Constraints and Uncertainty Po
I want to UPDATE or INSERT a column in PostgreSQL instead of doing INSERT or UPDATE using INSERT ... ON CONFLICT ... because there will be more updates than more inserts and also I have an auto incrementing id column that's defined using SERIAL so it increments the id column everytime it tries to INSERT or UPDATE and that's not what I want, I want the id col
The Prisma Client connection pool defaults to a fixed number of connections (commonly 10), and the documented timeout option governs query execution rather than the lifecycle of pooled connections. In a service handling bursts of concurrent queries alongside occasional long-running transactions, connections can remain checked out far longer than expected, an
I am reading about differences between JSON and JSONB datatypes on PostgreSql documentation https://www.postgresql.org/docs/13/datatype-json.html . There is this line The json data type stores an exact copy of the input text, which processing functions must reparse on each execution; while jsonb data is stored in a decomposed binary format that makes it slig
Goal is to make retried HTTP inserts from supabase-js safe against duplicate writes when PostgREST is used as the data API over PostgreSQL. The integration boundary has no transport-level idempotency. Idempotency is expected to be modeled in the database via a client-supplied key with a unique constraint and an upsert that maps to INSERT ... ON CONFLICT. The
There are a number of Heroku CLI Postgres commands that all return the same error. For example: $ heroku pg:bloat psql: FATAL: no pg_hba.conf entry for host "...", user "...", database "...", SSL off At least one of these commands has worked in the past, but does not now. The database appears to be working fine otherwise. I can access it via my application's
ory
yii
ecto
prisma
supabase
heroku