---
title: "postgres 4.1.1: release notes, upgrades and advisories"
description: "postgres 4.1.1: release notes, breaking changes by major version and no known security advisory."
url: https://inlinr.com/packages/postgres
lang: en
---

[Packages](https://inlinr.com/packages)

# postgres

4.1.1 · 11 Nov 2026 Unlicense 38.9M / week [Repository](https://github.com/porsager/postgres) [Homepage](https://github.com/porsager/postgres#readme) [npm](https://www.npmjs.com/package/postgres) [Atom feed](https://inlinr.com/packages/feed/postgres)

Your version 

## Where each line stands

[Plan an upgrade](https://inlinr.com/packages/postgres/upgrade)

LineNewestSecurity

- 4.x 4.1.1 No known advisory Latest line
- 3.x 3.4.9 No known advisory [To 4.1.1](https://inlinr.com/packages/postgres/upgrade/3.4.9-4.1.1)
- 1.x 1.0.2 No known advisory [To 4.1.1](https://inlinr.com/packages/postgres/upgrade/1.0.2-4.1.1)
- 0.x 0.0.1 No known advisory [To 4.1.1](https://inlinr.com/packages/postgres/upgrade/0.0.1-4.1.1)

## Latest releases

[All 36 releases](https://inlinr.com/packages/postgres/releases)

1. 4.x · latest line
2. ### [4.1.1](https://inlinr.com/packages/postgres/releases/4.1.1 "Open this release") [](https://github.com/porsager/postgres/releases/tag/v4.1.1 "Read this release where it was published")  
11 Nov 2026

  - **A statement `sql.begin` sends after its own `COMMIT` or `ROLLBACK` is rejected** ([#1320](https://github.com/porsager/postgres/issues/1320)). A statement the callback did not await, sent between the transaction's `COMMIT` or `ROLLBACK` and the release of its connection, ran outside the transaction, and after a rollback its write was kept. It now rejects with `UNSAFE_TRANSACTION`, as a statement after the transaction has ended does.
  - **A command after a select in a multi-statement simple query has no columns** ([#1321](https://github.com/porsager/postgres/issues/1321)). In `sql.unsafe('select …; rollback')` the `ROLLBACK` result had the columns of the `SELECT` before it.
  - **A query queued behind one with an untyped string or boolean parameter resolves on Cloudflare Hyperdrive** ([#1319](https://github.com/porsager/postgres/issues/1319)). Such a query is described first, and 4.1.0 sent its Bind, Execute and Sync together with the next query, which never resolved through Hyperdrive. On Cloudflare Workers the next query now waits until the described one is done, as in 3.4.9\. Other runtimes still pipeline it.
3. ### [4.1.0](https://inlinr.com/packages/postgres/releases/4.1.0 "Open this release") [](https://github.com/porsager/postgres/releases/tag/v4.1.0 "Read this release where it was published")  
5 Nov 2026  
Summary · from the note as AI read it  
Upgrade: this release fixes a security issue.
4. ### [4.0.0](https://inlinr.com/packages/postgres/releases/4.0.0 "Open this release") [](https://github.com/porsager/postgres/releases/tag/v4.0.0 "Read this release where it was published")  
29 Oct 2026  
Summary · from the note as AI read it  
Upgrade: this release fixes a security issue.

  - Security

**A NUL character in a connection parameter can no longer add parameters** (also in v3). A `database`, `user` or `connection` value such as `'db\0user\0postgres'` was sent as further startup parameters, so an app that put untrusted input there, as with a database per tenant, could be made to log in as another user where that user needs no password, or with `replication` or `options` set. A NUL in any protocol string, also in query text and identifiers, now rejects with `NUL_CHARACTER`.
  - Security

**A column named `__proto__` is an own property** (also in v3). It became the prototype of the row, so a JSON value in it, for instance from a column alias built from user input, made the row inherit its properties (`row.isAdmin`), in query results and in `sql.subscribe` rows alike.

Dependency tracking

## Know when your own dependencies move

postgres shipped a new major in the last 12 months, among 5 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.

- Advisories reach you  
An email when a critical or high advisory affects a project, before the next install.
- Upgrades checked first  
Peer ranges, Node, ESM-only and types changes read before you bump.
- Only what matters  
Majors and breaking notes stay; patches and sibling bumps fold into one line.

[How dependency tracking works](https://inlinr.com/dependencies)

## Security

No known security advisory.

## Health

[Details](https://inlinr.com/packages/postgres/security#signals)

- **Provenance**:
- **Publisher**:
- **Maintainers**:
- **Scorecard**:
- **Size**:

## Weekly downloads

Reading releases, release notes and advisories…

Registry facts last checked 20 Nov 2026\. Releases and advisories last read 20 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
