# porsager/postgres · Reposen Release & Migration Intelligence

> A statement `sql.begin` sends after its own `COMMIT` or `R. Drop-in upgrade. Migration: None.

## Metadata
- **Repository URL**: https://github.com/porsager/postgres
- **Primary Package**: `postgres` (NPM)
- **Categories**: `DATABASE`, `BACKEND`
- **Latest Version**: `v4.1.1`
- **Semantic Status**: `COMPATIBLE`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/porsager/postgres/releases.atom

## The Human Context (Plain-English Pitch)
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.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
A statement `sql.begin` sends after its own `COMMIT` or `R. Drop-in upgrade. Migration: None.

## Breaking Changes & Required Actions
- **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 `COMMIT` or `R...
- **A command after a select in a multi-statement simple query has no columns** (#1321). In `sql.unsafe('select …; rollback')` the `ROLLBACK` result 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...

## Migration Snippet
```ts
npm install postgres@4.1.1
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript 5.x** [`COMPATIBLE`]: Ships standard TypeScript declaration files without type regressions.

## Zero-Noise Release Timeline
- **v4.1.1** (2026-11-11) [COMPATIBLE]: A statement `sql.begin` sends after its own `COMMIT` or `R. Drop-in upgrade. Migration: None.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is 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
