postgres
4.1.1 · 11 Nov 2026Unlicense38.9M / weekRepositoryHomepagenpmAtom feed
Upgrading postgres From 1.0.2 to 3.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 14
- changes to make
- 0
- advisories fixed
- 1
- new
- 0
- fixes
Before you upgrade
Tick each one off as you go- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
Release by release
- Breaking
There are a few breaking changes from v2 beta, which some (myself included) was using in production, so I'm skipping a stable v2 release and going straight to v3.
- Breaking
Cursors are always called with
Resultarrays (previously cursor 1 would return a row object, where > 1 would return an array of rows) - Breaking
.writable()and.readable()is now async (returns a Promise that resolves to the stream) - Breaking
Queries now returns a lazy promise instead of being executed immediately. This means the query won't be sent until awaited (.then, .catch, .finally is called) or until
.execute()is manually called.
- Breaking
11 other lines we could not sort, mostly version bumps
- 3.0.0
Dynamic query builder based on raw sql
- 3.0.0
Realtime subscribe to db changes through logical replication
- 3.0.0
Multi-host support for High Availability setups
- 3.0.0
Postgres input parameter types from
ParameterDescription - 3.0.0
Deno support
- 3.0.0
Cursors as async iterators
- 3.0.0
.describe()to only get query input types and column definitions - 3.0.0
max_lifetimefor connections - 3.0.0
Cancellation of requests
- 3.0.0
Converted to ESM (with CJS support)
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.