Non-blocking PostgreSQL client for Node.js, implemented in pure JavaScript with optional native libpq bindings, provided under the node-postgres project (npm package `pg`). Useful for running parameterized queries and supporting common PostgreSQL features like connection pooling, async notifications (LISTEN/NOTIFY), and bulk import/export with COPY.
Project status
- Actively maintained: The upstream repo shows a recent push on 2026-06-22, and the monorepo has new updates as recently as 2026-06-19.
- Update cadence: Updates appear to be roughly monthly in the recent history (for example, 2026-05-18 to 2026-06-19), with additional upstream activity shortly after (2026-06-22).
AI summary generated
Recent updates
pg-connection-string@2.14.0
pg-connection-string version 2.14.0 was published, but no release notes were provided by the publisher. As a result, there is no documented information about new functionality, fixes, security changes, or migration requirements in this release.
pg-query-stream@4.16.0
pg-query-stream version 4.16.0 was published, but the publisher did not provide any release notes. Because no documented changes are available, you will need to review the upstream diff (or changelog/commits) to determine whether any API, behavior, or compatibility changes occurred.
pg-protocol@1.15.0
pg-protocol version 1.15.0 was released on 2026-06-19, but the publisher did not provide any release notes or change log details. As a result, this release cannot be assessed for new functionality, behavioral changes, or potential breaking changes based solely on the provided information.
pg-esm-test@1.8.0
pg-esm-test@1.8.0 was published, but the publisher did not provide release notes. There is no documented information about new functionality, bug fixes, breaking changes, or security updates in this release.
pg-cursor@2.21.0
pg-cursor v2.21.0 was released, but the publisher provided no release notes (no documented changes listed). Because there are no stated updates, API, behavior, or migration impacts cannot be verified from the release notes alone, and a code diff review is recommended before upgrading.
pg@8.22.0
pg@8.22.0 primarily introduces support for direct SSL negotiation via a new `sslnegotiation` option, including the necessary client connection flow changes for PostgreSQL 17+ servers. The release also includes protocol serialization and error-handling improvements, plus a small set of dependency bumps across the monorepo packages.
Featurespg@8.21.0
Release pg@8.21.0 was published on 2026-05-18. No release notes were provided by the publisher, so changes, fixes, or breaking impacts cannot be determined from the provided information.
pg-native@3.8.0
Release pg-native v3.8.0 was published on 2026-05-18. No release notes were provided by the publisher, so the changes included in this version cannot be determined from the release data alone.
pg-connection-string@2.13.0
Release pg-connection-string version 2.13.0 was published on 2026-05-18. No release notes were provided by the publisher, so the update content, potential breaking changes, and any fixes are not documented in this release description.
pg-cursor@2.20.0
Version 2.20.0 of pg-cursor was published on 2026-05-18. The publisher did not provide release notes, so this release cannot be evaluated for specific new features, bug fixes, breaking changes, security updates, or migration requirements based on the provided data.
pg-esm-test@1.7.0
This release (pg-esm-test@1.7.0) was published on 2026-05-18, but no release notes were provided. As a result, there are no documented new features, fixes, breaking changes, or dependency updates to assess from the publisher’s notes.
pg-protocol@1.14.0
The release notes for pg-protocol v1.14.0 were not provided by the publisher, so there is no documented information about changes, fixes, or upgrade requirements. To assess upgrade impact, you will likely need to review the tagged source diff (v1.13.x to v1.14.0) and any changelog in the repository itself.
pg-pool@3.14.0
The release notes for pg-pool 3.14.0 were not provided, so no specific changes (new features, fixes, breaking changes, or dependency updates) can be verified from the release notes alone. Developers should review the actual diff or changelog/release artifacts in the repository to assess upgrade impact.
pg-query-stream@4.15.0
No release notes were provided for pg-query-stream 4.15.0, so the specific code, API, or behavior changes are not described in the publisher material. As a result, it is not possible to reliably identify breaking changes, bug fixes, security updates, or dependency updates from the release notes alone.
pg-cloudflare@1.4.0
pg-cloudflare v1.4.0 was published on 2026-05-18, but the publisher did not provide any release notes in the available release data. No specific changes, fixes, or migration details can be extracted from the provided information, so developers should review the repository diff and release tags to assess upgrade risk.
pg-bundler-test@0.3.0
No release notes were provided for pg-bundler-test@0.3.0, so there is no documented information about changes, new features, fixes, or upgrade impacts. Developers should treat this release as opaque until they review the repository diff or published changelog elsewhere.