porsager/postgres
v4.1.1Curated database / backend repository (porsager/postgres) tracked via conditional GitHub .atom polling.
postgres is an open-source library and developer tool in the porsager/postgres ecosystem. It saves developers from writing repetitive low-level boilerplate from scratch by providing a battle-tested, open-source implementation ready for production.
A statement sql.begin sends after its own COMMIT or `R. Drop-in upgrade. Migration: None.
Key Release Highlights (v4.1.1)
- A statement `sql.begin` sends after its own `COMMIT` or `ROLLBACK` is rejected (#1320). A statement the callback did not await, sent between the transaction's
COMMITor `R... - A command after a select in a multi-statement simple query has no columns (#1321). In
sql.unsafe('select …; rollback')theROLLBACKresult had the columns of the `SELECT... - A query queued behind one with an untyped string or boolean parameter resolves on Cloudflare Hyperdrive (#1319). Such a query is described first, and 4.1.0 sent its Bind, Ex...
- `.cursor()` yields the rows of `SHOW`, `EXPLAIN` and other commands without a row count. Their last batch was only passed on when the command tag had a count, so a cursor ov...
Verified safe drop-in upgrade for postgres in package.json.
npm install postgres@4.1.1Ecosystem Compatibility Matrix & Verified Graph Warnings
Zero-Noise Historical Release Timeline (1)
Format: [Core Change] + [Required Action] + [Migration Effort]A statement sql.begin sends after its own COMMIT or `R. Drop-in upgrade. Migration: None.
Upgrade & Migration Q&A (porsager/postgres v4.1.1)
Direct Answers for Engineers & AI AgentsIs porsager/postgres v4.1.1 safe to upgrade in production?
porsager/postgres v4.1.1 is classified as COMPATIBLE (PATCH release). A statement sql.begin sends after its own COMMIT or `R. Drop-in upgrade. Migration: None.
What breaking changes or compatibility risks exist in porsager/postgres v4.1.1?
No breaking API changes or peer dependency conflicts are recorded for porsager/postgres v4.1.1 in the Reposen compatibility graph.
What is the bundle size impact of postgres v4.1.1?
Measured bundle size telemetry is currently unavailable for postgres v4.1.1; verify build output locally before deploying.
How do I upgrade postgres to v4.1.1?
Upgrade postgres to v4.1.1 by running "npm install postgres@4.1.1" and applying the migration steps: npm install postgres@4.1.1