npm - @steadybrew/postgresjs - Versions diffs - 4.5.0-rc1 → 4.5.1 - Mend

@steadybrew/postgresjs 4.5.0-rc1 → 4.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (19) hide show

package/README.md CHANGED Viewed

@@ -1,1746 +1,127 @@
-# Postgres.js by Steady Brew
-A maintained fork of [Postgres.js](https://github.com/porsager/postgres), the PostgreSQL client created by [Rasmus Porsager](https://github.com/porsager), with the same API.
-- **Fixes reported Postgres.js bugs:** 40 open upstream issues, from queries receiving another query's rows to hung pools and crashed processes, each covered by a regression test. See [the list](#fixed-postgresjs-issues).
-- **Built for serverless and connection poolers:** bounded connection retries with backoff, idle connections replaced when a frozen instance resumes, pool statistics from `sql.stats()`, and an adapter for Vercel Fluid. Query timeouts and cancellable pool waits are next on the [roadmap](ROADMAP.md).
-- **Switch with one line:** your code and the libraries that import `postgres` keep working. See [Switching from Postgres.js](#switching-from-postgresjs).
----
+<p align="center">
+  <img width="440" height="180" alt="Postgres.js" src="postgresjs.svg">
+</p>
-<img align="left" width="440" height="180" alt="Fastest full PostgreSQL nodejs client" src="https://raw.githubusercontent.com/porsager/postgres/master/postgresjs.svg?sanitize=true">
-- [🚀 Fastest full-featured node & deno client](https://github.com/porsager/postgres-benchmarks#results)
-- 🏷 ES6 Tagged Template Strings at the core
-- 🏄‍♀️ Simple surface API
-- 🖊️ Dynamic query support
-<br clear="all">
-## Compatibility
+# Postgres.js by Steady Brew
 [![test](https://github.com/steadybrew/postgresjs/actions/workflows/test.yml/badge.svg?branch=main)](https://github.com/steadybrew/postgresjs/actions/workflows/test.yml?query=branch%3Amain)
-**Version 4 runs on Node.js 22 or newer** and supports PostgreSQL 15–18. Every release passes the full test matrix before it is published.
-| Runtime | PostgreSQL | Notes |
-| --- | --- | --- |
-| Node 22, 24 and 26, ESM and CJS | 15–18 | |
-| Deno 1.46.3 | 17 | No Deno 2 claim |
-| Cloudflare Workers (workerd) | 17 | A "Stream was cancelled" rejection on socket close remains ([#1196](https://github.com/porsager/postgres/issues/1196), [#1202](https://github.com/porsager/postgres/issues/1202)) |
-| Bun | | Best effort, not tested in CI |
-[The test workflow](https://github.com/steadybrew/postgresjs/blob/main/.github/workflows/test.yml) defines which pairs run on each push. Supabase PostgreSQL and Supabase Edge are separate environments; Deno 1.46.3 coverage does not imply Deno 2 or hosted Supabase Edge.
-## Switching from Postgres.js
+**Keep the [Postgres.js](https://github.com/porsager/postgres) API by [Rasmus Porsager](https://github.com/porsager) and get critical fixes and new features:**
-```sh
-npm install postgres@npm:@steadybrew/postgresjs@^4
-```
+- **Correctness fixes.** Queries get the right results, transactions stay isolated, and rollbacks are reported as failures.
+- **Fewer hangs and crashes.** Fixes for stuck queries, shutdown hangs and crashes after disconnects.
+- **Pool monitoring.** See busy connections, idle connections and waiting queries with `sql.stats()`.
+- **Faster queries behind poolers.** Removes an extra network round trip for supported values (opt-in).
+- **Vercel Fluid Compute support.** Reuse connections between requests and close idle ones before suspension to avoid connection leaks.
-This installs the fork under the name `postgres`, so `import postgres from 'postgres'` stays as it is, and so do libraries that import it, such as `drizzle-orm/postgres-js`, `drizzle-kit` and `kysely-postgres-js`. Then read [Upgrading to 4.0.0](#upgrading-to-400) for the behaviour changes.
+**[50+ reported upstream bugs fixed](docs/fixed-issues.md)**, with regression tests.
-Tracing: from 4.5.0, dd-trace records the same database spans as with Postgres.js when the fork is installed under the `postgres` name. Sentry's automatic integration instruments `postgres` versions below 4 only, so widen its range before Sentry loads:
+[Start a new project](#start-a-new-project) · [Switch from Postgres.js](#switching-from-postgresjs) · [Why this fork](#why-this-fork) · [API reference](docs/api.md) · [Roadmap](ROADMAP.md)
-```js
-// sentry-postgres.mjs
-import { SENTRY_RUNTIME_INSTRUMENTATIONS } from '@sentry/server-utils/orchestrion/config'
+<a id="install"></a>
-for (const instrumentation of SENTRY_RUNTIME_INSTRUMENTATIONS) {
-  if (instrumentation.module.name === 'postgres')
-    instrumentation.module.versionRange = '>=3.0.0 <5'
-}
-```
+## Start a new project
 ```sh
-node --import ./sentry-postgres.mjs --import @sentry/node/import app.js
-```
-This covers Sentry's runtime hook, not its bundler plugins. With pnpm, add `@sentry/server-utils` at the same version as `@sentry/node` so the file can import it.
-## Upgrading to 4.0.0
-Version 4.0.0 fixes connection startup, reservations, reconnects, shutdown, transaction ownership, and built-in array handling. When upgrading from Postgres.js 3.4 or `@steadybrew/postgresjs` 3.x:
-- Upgrade to **Node.js 22 or newer** before installing.
-- Keep queries within the reservation or transaction that owns them. Reserved handles used after `release()`, and transaction handles used after completion, reject with `CONNECTION_ENDED`. A handle whose connection has closed cannot run queries on a reconnected session.
-- Pass a non-empty string without NUL characters to transaction `sql.prepare(name)`. Invalid names throw `INVALID_TRANSACTION_NAME`.
-- If you use `fetch_types: false`, review code that expects built-in arrays as raw strings: supported built-in arrays are now decoded as JavaScript arrays. SQL `NULL` elements become JavaScript `null`; quoted `"NULL"` text remains a string.
-See the [changelog](./CHANGELOG.md#breaking-changes-and-migration) for the full migration notes and fixes.
-## Fixed Postgres.js issues
-Upstream issues on [porsager/postgres](https://github.com/porsager/postgres/issues) that this fork fixes, and the version that fixed them. Each fix has a test that reproduces the report. The [changelog](./CHANGELOG.md) has the details.
-<details>
-<summary>40 bugs and 4 feature requests</summary>
-**Wrong results and data safety**
-| Issue | What happens now | Since |
-| --- | --- | --- |
-| [#1082](https://github.com/porsager/postgres/issues/1082), [#729](https://github.com/porsager/postgres/issues/729) | A query whose values fail to serialize rejects on its own; the query running alongside no longer gets its error, and the next query no longer gets another query's rows | 4.3.0 |
-| [#1216](https://github.com/porsager/postgres/issues/1216) | A transaction handle whose connection closed can't run on a reconnected session, so it can't read another user's rows through RLS | 4.0.0 |
-| [#1248](https://github.com/porsager/postgres/issues/1248) | Statements in a `sql.begin()` callback after its connection closes reject instead of running outside the transaction | 4.0.0 |
-| [#1204](https://github.com/porsager/postgres/issues/1204) | A transaction's connection is never handed to another transaction | 4.0.0 |
-| [#1217](https://github.com/porsager/postgres/issues/1217) | `sql.begin()` rejects with `TRANSACTION_ROLLED_BACK` when the server rolled back the COMMIT | 4.4.0 |
-| [#1249](https://github.com/porsager/postgres/issues/1249), [#1226](https://github.com/porsager/postgres/issues/1226), [#1223](https://github.com/porsager/postgres/issues/1223) | The first query after a reconnect no longer rejects with an error from the closed session | 4.0.0 |
-| [#789](https://github.com/porsager/postgres/issues/789) | `sql.array()` infers the right array type on first use | 4.0.0 |
-**Hangs**
-| Issue | What happens now | Since |
-| --- | --- | --- |
-| [#751](https://github.com/porsager/postgres/issues/751), [#1219](https://github.com/porsager/postgres/issues/1219), [#1203](https://github.com/porsager/postgres/issues/1203) | `sql.reserve()` on a pool that hasn't opened a connection yet resolves, with or without `fetch_types` and on Cloudflare Workers | 4.0.0 |
-| [#1195](https://github.com/porsager/postgres/issues/1195), [#1199](https://github.com/porsager/postgres/issues/1199) | A reservation survives its connection being terminated by the server, and the pool recovers after it is released | 4.0.0 |
-| [#1186](https://github.com/porsager/postgres/issues/1186) | Queries queued on a reserved or transaction handle settle when its connection closes | 4.0.0 |
-| [#1097](https://github.com/porsager/postgres/issues/1097), [#1130](https://github.com/porsager/postgres/issues/1130), [#1242](https://github.com/porsager/postgres/issues/1242), [#861](https://github.com/porsager/postgres/issues/861) | `sql.end()` resolves after a disconnect, after a failed query and after a connection closes inside `sql.begin()`, and waits for queries queued in the pool | 4.0.0 |
-| [#1246](https://github.com/porsager/postgres/issues/1246) | A query sent between a socket error and its close settles | 4.1.0 |
-| [#1193](https://github.com/porsager/postgres/issues/1193) | A connection closed during startup settles its first query instead of reconnecting in a tight loop | 4.0.0 |
-| [#1234](https://github.com/porsager/postgres/issues/1234) | Concurrent queries in `sql.begin()` after a column type change roll the transaction back and return the connection to the pool | 4.4.0 |
-**Crashes**
-| Issue | What happens now | Since |
-| --- | --- | --- |
-| [#1066](https://github.com/porsager/postgres/issues/1066), [#1154](https://github.com/porsager/postgres/issues/1154), [#1208](https://github.com/porsager/postgres/issues/1208), [#1133](https://github.com/porsager/postgres/issues/1133) | A reserved or transaction handle whose backend died rejects its statements instead of throwing an uncaught exception | 4.0.0 |
-| [#1192](https://github.com/porsager/postgres/issues/1192), [#1205](https://github.com/porsager/postgres/issues/1205), [#1086](https://github.com/porsager/postgres/issues/1086) | A failed or cancelled type query at startup rejects the query instead of crashing the process | 4.0.0 |
-| [#1088](https://github.com/porsager/postgres/issues/1088) | Timers no longer fail on Cloudflare Workers | 4.0.0 |
-**Reconnects and failover**
-| Issue | What happens now | Since |
-| --- | --- | --- |
-| [#1179](https://github.com/porsager/postgres/issues/1179) | Failed connection attempts back off instead of the whole pool retrying at once | 4.0.0 |
-| [#1174](https://github.com/porsager/postgres/issues/1174), [#815](https://github.com/porsager/postgres/issues/815), [#988](https://github.com/porsager/postgres/issues/988) | With several hosts, retries move to the next host, a connect timeout fails over, and `prefer-standby` falls back to a primary | 4.0.0 |
-**Transactions, notices and subscriptions**
-| Issue | What happens now | Since |
-| --- | --- | --- |
-| [#823](https://github.com/porsager/postgres/issues/823), [#1189](https://github.com/porsager/postgres/issues/1189), [#1210](https://github.com/porsager/postgres/issues/1210) | `sql.begin()` no longer fails with `UNSAFE_TRANSACTION` under write backpressure or with `max_pipeline: 0` | 4.0.0 |
-| [#1063](https://github.com/porsager/postgres/issues/1063) | `onnotice: false` silences notices | 4.4.0 |
-| [#1087](https://github.com/porsager/postgres/issues/1087) | `sql.subscribe()` no longer adds a listener on each subscribe or loses changes after a transform throws | 4.4.0 |
-**Feature requests**
-| Issue | What you get | Since |
-| --- | --- | --- |
-| [#443](https://github.com/porsager/postgres/issues/443), [#908](https://github.com/porsager/postgres/issues/908) | `sql.stats()` reports connections in use and idle, and queries waiting | 4.3.0 |
-| [#1100](https://github.com/porsager/postgres/issues/1100) | An `onidle` callback and the `@steadybrew/postgresjs/vercel` adapter | 4.2.0 |
-| [#1164](https://github.com/porsager/postgres/issues/1164) | Built-in array types are decoded with `fetch_types: false` | 4.0.0 |
-</details>
-## Getting started
-<br>
-<img height="220" width="458" alt="Good UX with Postgres.js" src="https://raw.githubusercontent.com/porsager/postgres/master/demo.gif">
-<br>
-### Installation
-```bash
-$ npm install @steadybrew/postgresjs
-```
-### Usage
-Create your `sql` database instance
-```js
-// db.js
-import postgres from '@steadybrew/postgresjs'
-const sql = postgres({ /* options */ }) // will use psql environment variables
-export default sql
-```
-Simply import for use elsewhere
-```js
-// users.js
-import sql from './db.js'
-async function getUsersOver(age) {
-  const users = await sql`
-    select
-      name,
-      age
-    from users
-    where age > ${ age }
-  `
-  // users = Result [{ name: "Walter", age: 80 }, { name: 'Murray', age: 68 }, ...]
-  return users
-}
-async function insertUser({ name, age }) {
-  const users = await sql`
-    insert into users
-      (name, age)
-    values
-      (${ name }, ${ age })
-    returning name, age
-  `
-  // users = Result [{ name: "Murray", age: 68 }]
-  return users
-}
-```
-#### ESM dynamic imports
-The library can be used with ESM dynamic imports as well as shown here.
-```js
-const { default: postgres } = await import('@steadybrew/postgresjs')
-```
-## Table of Contents
-* [Upgrading to 4.0.0](#upgrading-to-400)
-* [Connection](#connection)
-* [Queries](#queries)
-* [Building queries](#building-queries)
-* [Advanced query methods](#advanced-query-methods)
-* [Transactions](#transactions)
-* [Data Transformation](#data-transformation)
-* [Listen & notify](#listen--notify)
-* [Realtime subscribe](#realtime-subscribe)
-* [Numbers, bigint, numeric](#numbers-bigint-numeric)
-* [Parameter types](#parameter-types)
-* [Result Array](#result-array)
-* [Connection details](#connection-details)
-* [Custom Types](#custom-types)
-* [Teardown / Cleanup](#teardown--cleanup)
-* [Error handling](#error-handling)
-* [TypeScript support](#typescript-support)
-* [Reserving connections](#reserving-connections)
-* [Changelog](./CHANGELOG.md)
-## Connection
-### `postgres([url], [options])`
-You can use either a `postgres://` url connection string or the options to define your database connection properties. Options in the object will override any present in the url. Options will fall back to the same environment variables as psql.
-```js
-const sql = postgres('postgres://username:password@host:port/database', {
-  host                 : '',            // Postgres ip address[s] or domain name[s]
-  port                 : 5432,          // Postgres server port[s]
-  database             : '',            // Name of database to connect to
-  username             : '',            // Username of database user
-  password             : '',            // Password of database user
-  ...and more
-})
-```
-More options can be found in the [Connection details section](#connection-details).
-## Queries
-### ```await sql`...` -> Result[]```
-Postgres.js utilizes [Tagged template functions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals#Tagged_templates) to process query parameters **before** interpolation. Using tagged template literals benefits developers by:
-1. **Enforcing** safe query generation
-2. Giving the ` sql`` ` function powerful [utility](#dynamic-inserts) and [query building](#building-queries) features.
-Any generic value will be serialized as described in [Parameter types](#parameter-types), and replaced by a PostgreSQL protocol placeholder `$1, $2, ...`. The values are then sent separately to PostgreSQL, which handles escaping & casting.
-All queries will return a `Result` array, with objects mapping column names to each row.
-```js
-const xs = await sql`
-  insert into users (
-    name, age
-  ) values (
-    'Murray', 68
-  )
-  returning *
-`
-// xs = [{ user_id: 1, name: 'Murray', age: 68 }]
-```
-> Please note that queries are first executed when `awaited` – or instantly by using [`.execute()`](#execute).
-### Query parameters
-Parameters are automatically extracted and handled by the database so that SQL injection isn't possible. No special handling is necessary, simply use tagged template literals as usual.
-```js
-const name = 'Mur'
-    , age = 60
-const users = await sql`
-  select
-    name,
-    age
-  from users
-  where
-    name like ${ name + '%' }
-    and age > ${ age }
-`
-// users = [{ name: 'Murray', age: 68 }]
-```
-> Be careful with quotation marks here. Because Postgres infers column types, you do not need to wrap your interpolated parameters in quotes like `'${name}'`. This will cause an error because the tagged template replaces `${name}` with `$1` in the query string, leaving Postgres to do the interpolation. If you wrap that in a string, Postgres will see `'$1'` and interpret it as a string as opposed to a parameter.
-### Dynamic column selection
-```js
-const columns = ['name', 'age']
-await sql`
-  select
-    ${ sql(columns) }
-  from users
-`
-// Which results in:
-select "name", "age" from users
-```
-### Dynamic inserts
-```js
-const user = {
-  name: 'Murray',
-  age: 68
-}
-await sql`
-  insert into users ${
-    sql(user, 'name', 'age')
-  }
-`
-// Which results in:
-insert into users ("name", "age") values ($1, $2)
-// The columns can also be given with an array
-const columns = ['name', 'age']
-await sql`
-  insert into users ${
-    sql(user, columns)
-  }
-`
-```
-**You can omit column names and simply execute `sql(user)` to get all the fields from the object as columns**. Be careful not to allow users to supply columns that you do not want to be inserted.
-#### Multiple inserts in one query
-If you need to insert multiple rows at the same time it's also much faster to do it with a single `insert`. Simply pass an array of objects to `sql()`.
-```js
-const users = [{
-  name: 'Murray',
-  age: 68,
-  garbage: 'ignore'
-},
-{
-  name: 'Walter',
-  age: 80
-}]
-await sql`insert into users ${ sql(users, 'name', 'age') }`
-// Is translated to:
-insert into users ("name", "age") values ($1, $2), ($3, $4)
-// Here you can also omit column names which will use object keys as columns
-await sql`insert into users ${ sql(users) }`
-// Which results in:
-insert into users ("name", "age") values ($1, $2), ($3, $4)
-```
-### Dynamic columns in updates
-This is also useful for update queries
-```js
-const user = {
-  id: 1,
-  name: 'Murray',
-  age: 68
-}
-await sql`
-  update users set ${
-    sql(user, 'name', 'age')
-  }
-  where user_id = ${ user.id }
-`
-// Which results in:
-update users set "name" = $1, "age" = $2 where user_id = $3
-// The columns can also be given with an array
-const columns = ['name', 'age']
-await sql`
-  update users set ${
-    sql(user, columns)
-  }
-  where user_id = ${ user.id }
-`
-```
-### Multiple updates in one query
-To create multiple updates in a single query, it is necessary to use arrays instead of objects to ensure that the order of the items correspond with the column names.
-```js
-const users = [
-  [1, 'John', 34],
-  [2, 'Jane', 27],
-]
-await sql`
-  update users set name = update_data.name, age = (update_data.age)::int
-  from (values ${sql(users)}) as update_data (id, name, age)
-  where users.id = (update_data.id)::int
-  returning users.id, users.name, users.age
-`
-```
-### Dynamic values and `where in`
-Value lists can also be created dynamically, making `where in` queries simple too.
-```js
-const users = await sql`
-  select
-    *
-  from users
-  where age in ${ sql([68, 75, 23]) }
-`
-```
-or
-```js
-const [{ a, b, c }] = await sql`
-  select
-    *
-  from (values ${ sql(['a', 'b', 'c']) }) as x(a, b, c)
-`
+npm install @steadybrew/postgresjs
 ```
-## Building queries
+Or, for Drizzle or Kysely, use the alias:
-Postgres.js features a simple dynamic query builder by conditionally appending/omitting query fragments.
-It works by nesting ` sql`` ` fragments within other ` sql`` ` calls or fragments. This allows you to build dynamic queries safely without risking sql injections through usual string concatenation.
-### Partial queries
-```js
-const olderThan = x => sql`and age > ${ x }`
-const filterAge = true
-await sql`
-  select
-   *
-  from users
-  where name is not null ${
-    filterAge
-      ? olderThan(50)
-      : sql``
-  }
-`
-// Which results in:
-select * from users where name is not null
-// Or
-select * from users where name is not null and age > 50
-```
-### Dynamic filters
-```js
-await sql`
-  select
-    *
-  from users ${
-    id
-      ? sql`where user_id = ${ id }`
-      : sql``
-  }
-`
-// Which results in:
-select * from users
-// Or
-select * from users where user_id = $1
-```
-### Dynamic ordering
-```js
-const id = 1
-const order = {
-  username: 'asc'
-  created_at: 'desc'
-}
-await sql`
-  select
-    *
-  from ticket
-  where account = ${ id }
-  order by ${
-    Object.entries(order).flatMap(([column, order], i) =>
-      [i ? sql`,` : sql``, sql`${ sql(column) } ${ order === 'desc' ? sql`desc` : sql`asc` }`]
-    )
-  }
-`
-```
-### SQL functions
-Using keywords or calling functions dynamically is also possible by using ``` sql`` ``` fragments.
-```js
-const date = null
-await sql`
-  update users set updated_at = ${ date || sql`now()` }
-`
-// Which results in:
-update users set updated_at = now()
-```
-### Table names
-Dynamic identifiers like table names and column names is also supported like so:
-```js
-const table = 'users'
-    , column = 'id'
-await sql`
-  select ${ sql(column) } from ${ sql(table) }
-`
-// Which results in:
-select "id" from "users"
-```
-### Quick primer on interpolation
-Here's a quick oversight over all the ways to do interpolation in a query template string:
-| Interpolation syntax       | Usage                         | Example                                                   |
-| -------------              | -------------                 | -------------                                             |
-| `${ sql`` }`               | for keywords or sql fragments | ``await sql`SELECT * FROM users ${sql`order by age desc` }` ``  |
-| `${ sql(string) }`         | for identifiers               | ``await sql`SELECT * FROM ${sql('table_name')` ``               |
-| `${ sql([] or {}, ...) }`  | for helpers                   | ``await sql`INSERT INTO users ${sql({ name: 'Peter'})}` ``      |
-| `${ 'somevalue' }`         | for values                    | ``await sql`SELECT * FROM users WHERE age = ${42}` ``           |
-## Advanced query methods
-### Cursors
-#### ```await sql``.cursor([rows = 1], [fn])```
-Use cursors if you need to throttle the amount of rows being returned from a query. You can use a cursor either as an [async iterable](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for-await...of) or with a callback function. For a callback function new results won't be requested until the promise / async callback function has resolved.
-##### callback function
-```js
-await sql`
-  select
-    *
-  from generate_series(1,4) as x
-`.cursor(async([row]) => {
-  // row = { x: 1 }
-  await http.request('https://example.com/wat', { row })
-})
-```
-##### for await...of
-```js
-// for await...of
-const cursor = sql`select * from generate_series(1,4) as x`.cursor()
-for await (const [row] of cursor) {
-  // row = { x: 1 }
-  await http.request('https://example.com/wat', { row })
-}
-```
-A single row will be returned by default, but you can also request batches by setting the number of rows desired in each batch as the first argument to `.cursor`:
-```js
-await sql`
-  select
-    *
-  from generate_series(1,1000) as x
-`.cursor(10, async rows => {
-  // rows = [{ x: 1 }, { x: 2 }, ... ]
-  await Promise.all(rows.map(row =>
-    http.request('https://example.com/wat', { row })
-  ))
-})
-```
-If an error is thrown inside the callback function no more rows will be requested and the outer promise will reject with the thrown error.
-You can close the cursor early either by calling `break` in the `for await...of` loop, or by returning the token `sql.CLOSE` from the callback function.
-```js
-await sql`
-  select * from generate_series(1,1000) as x
-`.cursor(row => {
-  return Math.random() > 0.9 && sql.CLOSE // or sql.END
-})
-```
-### Instant iteration
-#### ```await sql``.forEach(fn)```
-If you want to handle rows returned by a query one by one, you can use `.forEach` which returns a promise that resolves once there are no more rows.
-```js
-await sql`
-  select created_at, name from events
-`.forEach(row => {
-  // row = { created_at: '2019-11-22T14:22:00Z', name: 'connected' }
-})
-// No more rows
-```
-### Query Descriptions
-#### ```await sql``.describe() -> Result[]```
-Rather than executing a given query, `.describe` will return information utilized in the query process. This information can include the query identifier, column types, etc.
-This is useful for debugging and analyzing your Postgres queries. Furthermore, **`.describe` will give you access to the final generated query string that would be executed.**
-### Rows as Array of Values
-#### ```sql``.values()```
-Using `.values` will return rows as an array of values for each column, instead of objects.
-This can be useful to receive identically named columns, or for specific performance/transformation reasons. The column definitions are still included on the result array, plus access to parsers for each column.
-### Rows as Raw Array of Buffers
-#### ```sql``.raw()```
-Using `.raw` will return rows as an array with `Buffer` values for each column, instead of objects.
-This can be useful for specific performance/transformation reasons. The column definitions are still included on the result array, plus access to parsers for each column.
-### Queries in Files
-#### `await sql.file(path, [args], [options]) -> Result[]`
-Using a file for a query is also supported with optional parameters to use if the file includes `$1, $2, etc`
-```js
-const result = await sql.file('query.sql', ['Murray', 68])
-```
-### Multiple statements in one query
-#### ```await sql``.simple()```
-The postgres wire protocol supports ["simple"](https://www.postgresql.org/docs/current/protocol-flow.html#id-1.10.6.7.4) and ["extended"](https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY) queries. "simple" queries supports multiple statements, but does not support any dynamic parameters. "extended" queries support parameters but only one statement. To use "simple" queries you can use
-```sql``.simple()```. That will create it as a simple query.
-```js
-await sql`select 1; select 2;`.simple()
-```
-### Copy to/from as Streams
-Postgres.js supports [`COPY ...`](https://www.postgresql.org/docs/14/sql-copy.html) queries, which are exposed as [Node.js streams](https://nodejs.org/api/stream.html).
-#### ```await sql`copy ... from stdin`.writable() -> Writable```
-```js
-import { pipeline } from 'node:stream/promises'
-// Stream of users with the default tab delimitated cells and new-line delimitated rows
-const userStream = Readable.from([
-  'Murray\t68\n',
-  'Walter\t80\n'
-])
-const query = await sql`copy users (name, age) from stdin`.writable()
-await pipeline(userStream, query);
-```
-#### ```await sql`copy ... to stdout`.readable() -> Readable```
-##### Using Stream Pipeline
-```js
-import { pipeline } from 'node:stream/promises'
-import { createWriteStream } from 'node:fs'
-const readableStream = await sql`copy users (name, age) to stdout`.readable()
-await pipeline(readableStream, createWriteStream('output.tsv'))
-// output.tsv content: `Murray\t68\nWalter\t80\n`
-```
-##### Using `for await...of`
-```js
-const readableStream = await sql`
-  copy (
-    select name, age
-    from users
-    where age = 68
-  ) to stdout
-`.readable()
-for await (const chunk of readableStream) {
-  // chunk.toString() === `Murray\t68\n`
-}
-```
-> **NOTE** This is a low-level API which does not provide any type safety. To make this work, you must match your [`copy query` parameters](https://www.postgresql.org/docs/14/sql-copy.html) correctly to your [Node.js stream read or write](https://nodejs.org/api/stream.html) code. Ensure [Node.js stream backpressure](https://nodejs.org/en/learn/modules/backpressuring-in-streams) is handled correctly to avoid memory exhaustion.
-A `COPY` holds its connection until it finishes. Postgres.js cannot tell that a simple-protocol query is a `COPY` until the server answers, so it sends nothing behind a simple query whose text contains the word `copy` (`sql.unsafe()` or `sql.file()` without parameters, `.simple()`, `.readable()`, `.writable()`). Queries sent through `sql` meanwhile run on another connection or wait for one. When every connection is running a `COPY` that has not been ended, for example with `max: 1`, queries, `sql.reserve()` and `sql.begin()` through `sql` reject with `COPY_IN_PROGRESS` instead, because only that `COPY` finishing could free a connection. Statements on a `sql.reserve()` or `sql.begin()` handle reject with `COPY_IN_PROGRESS` while its `COPY` runs.
-### Canceling Queries in Progress
-Postgres.js supports, [canceling queries in progress](https://www.postgresql.org/docs/7.1/protocol-protocol.html#AEN39000). It works by opening a new connection with a protocol level startup message to cancel the current query running on a specific connection. That means there is no guarantee that the query will be canceled, and due to the possible race conditions it might even result in canceling another query. This is fine for long running queries, but in the case of high load and fast queries it might be better to simply ignore results instead of canceling.
-```js
-const query = sql`select pg_sleep 100`.execute()
-setTimeout(() => query.cancel(), 100)
-const result = await query
-```
-### Execute
-#### ```await sql``.execute()```
-The lazy Promise implementation in Postgres.js is what allows it to distinguish [Nested Fragments](#building-queries) from the main outer query. This also means that queries are always executed at the earliest in the following tick. If you have a specific need to execute the query in the same tick, you can call `.execute()`
-### Unsafe raw string queries
-<details>
-<summary>Advanced unsafe use cases</summary>
-### `await sql.unsafe(query, [args], [options]) -> Result[]`
-If you know what you're doing, you can use `unsafe` to pass any string you'd like to postgres. Please note that this can lead to SQL injection if you're not careful.
-```js
-sql.unsafe('select ' + danger + ' from users where id = ' + dragons)
+```sh
+npm install postgres@npm:@steadybrew/postgresjs@^4
 ```
-By default, `sql.unsafe` assumes the `query` string is sufficiently dynamic that prepared statements do not make sense, and so defaults them to off. If you'd like to re-enable prepared statements, you can pass `{ prepare: true }`.
-You can also nest `sql.unsafe` within a safe `sql` expression.  This is useful if only part of your fraction has unsafe elements.
 ```js
-const triggerName = 'friend_created'
-const triggerFnName = 'on_friend_created'
-const eventType = 'insert'
-const schema_name = 'app'
-const table_name = 'friends'
+import postgres from '@steadybrew/postgresjs' // or 'postgres' with the alias
-await sql`
-  create or replace trigger ${sql(triggerName)}
-  after ${sql.unsafe(eventType)} on ${sql.unsafe(`${schema_name}.${table_name}`)}
-  for each row
-  execute function ${sql(triggerFnName)}()
-`
+const sql = postgres(process.env.DATABASE_URL)
-await sql`
-  create role friend_service with login password ${sql.unsafe(`'${password}'`)}
-`
+const minAge = 18
+const users = await sql`select name, age from users where age >= ${ minAge }`
 ```
-</details>
-## Transactions
-#### BEGIN / COMMIT `await sql.begin([options = ''], fn) -> fn()`
-Use `sql.begin` to start a new transaction. Postgres.js will reserve a connection for the transaction and supply a scoped `sql` instance for all transaction uses in the callback function. `sql.begin` will resolve with the returned value from the callback function.
-`BEGIN` is automatically sent with the optional options, and if anything fails `ROLLBACK` will be called so the connection can be released and execution can continue.
-```js
-const [user, account] = await sql.begin(async sql => {
-  const [user] = await sql`
-    insert into users (
-      name
-    ) values (
-      'Murray'
-    )
-    returning *
-  `
+## Switching from Postgres.js
-  const [account] = await sql`
-    insert into accounts (
-      user_id
-    ) values (
-      ${ user.user_id }
-    )
-    returning *
-  `
+**Check first.** The [migration codemod](codemod/README.md) reports required changes, behaviour differences to review and useful fixes, with file and line. It changes nothing:
-  return [user, account]
-})
+```sh
+npx @steadybrew/postgresjs-migrate .
 ```
-Do note that you can often achieve the same result using [`WITH` queries (Common Table Expressions)](https://www.postgresql.org/docs/current/queries-with.html) instead of using transactions.
+**Then migrate with Codemod:**
-It's also possible to pipeline the requests in a transaction if needed by returning an array with queries from the callback function like this:
-```js
-const result = await sql.begin(sql => [
-  sql`update ...`,
-  sql`update ...`,
-  sql`insert ...`
-])
+```sh
+npx codemod @steadybrew/postgresjs-migrate
 ```
-#### SAVEPOINT `await sql.savepoint([name], fn) -> fn()`
-```js
-sql.begin('read write', async sql => {
-  const [user] = await sql`
-    insert into users (
-      name
-    ) values (
-      'Murray'
-    )
-  `
-  const [account] = (await sql.savepoint(sql =>
-    sql`
-      insert into accounts (
-        user_id
-      ) values (
-        ${ user.user_id }
-      )
-    `
-  ).catch(err => {
-    // Account could not be created. ROLLBACK SAVEPOINT is called because we caught the rejection.
-  })) || []
+Run it from your project root. It checks again, switches dependencies and overrides to the fork, and removes patches already covered by the fork. Your source code and imports stay unchanged. Run your package manager's install afterwards to update the lockfile.
-  return [user, account]
-})
-.then(([user, account]) => {
-  // great success - COMMIT succeeded
-})
-.catch(() => {
-  // not so good - ROLLBACK was called
-})
-```
+<a id="upgrading-to-400"></a>
+See the [migration guide](docs/upgrading.md) for behaviour changes, manual installation and the direct npm CLI.
-#### PREPARE TRANSACTION `sql.prepare(name)`
+### Drizzle, Kysely and tracing
-Indicates that the transactions should be prepared using the [`PREPARE TRANSACTION [NAME]`](https://www.postgresql.org/docs/current/sql-prepare-transaction.html) statement
-instead of being committed.
+The alias above works with `drizzle-orm/postgres-js`, `drizzle-kit`, `kysely-postgres-js` and dd-trace. The codemod sets it up for existing projects, preserving `import postgres from 'postgres'`.
-The name must be a non-empty string without NUL characters; invalid names throw `INVALID_TRANSACTION_NAME`. Quotes and backslashes in valid names are preserved.
+**Sentry needs an extra step:** add the [tracing preload](docs/upgrading.md#tracing) to retain automatic database spans. The codemod flags Sentry but does **not** apply this adjustment.
-```js
-sql.begin('read write', async sql => {
-  const [user] = await sql`
-    insert into users (
-      name
-    ) values (
-      'Murray'
-    )
-  `
+## Security
-  await sql.prepare('tx1')
-})
-```
+Published from GitHub Actions through npm trusted publishing, with provenance and maintainer approval using two-factor authentication. No stored npm token, runtime dependencies or registry install scripts. Verify with `npm audit signatures`.
-## Data Transformation
+[Changes since upstream 3.4.9](https://github.com/steadybrew/postgresjs/compare/v3.4.9...main) · [Report a vulnerability](SECURITY.md) · [Unlicense](UNLICENSE)
-Postgres.js allows for transformation of the data passed to or returned from a query by using the `transform` option.
+## Compatibility
-Built in transformation functions are:
+Releases pass the [test matrix](.github/workflows/test.yml) before publishing:
-* For camelCase - `postgres.camel`, `postgres.toCamel`, `postgres.fromCamel`
-* For PascalCase - `postgres.pascal`, `postgres.toPascal`, `postgres.fromPascal`
-* For Kebab-Case - `postgres.kebab`, `postgres.toKebab`, `postgres.fromKebab`
+| Runtime | PostgreSQL tested |
+| --- | --- |
+| Node.js 22, 24 and 26, ESM and CommonJS | 15–18 |
+| Deno 1.46.3 | 17 |
+| Cloudflare Workers (workerd) | 17 |
-These built in transformations will only convert to/from snake_case. For example, using `{ transform: postgres.toCamel }` will convert the column names to camelCase only if the column names are in snake_case to begin with. `{ transform: postgres.fromCamel }` will convert camelCase only to snake_case.
+TypeScript declarations are included; use `@types/node` 22+ or `skipLibCheck`.
-By default, using `postgres.camel`, `postgres.pascal` and `postgres.kebab` will perform a two-way transformation - both the data passed to the query and the data returned by the query will be transformed:
+Older Node.js versions may work but aren't tested. The package declares `engines.node: >=22`, so package managers may warn or reject installation on older versions.
-```js
-// Transform the column names to and from camel case
-const sql = postgres({ transform: postgres.camel })
+Hosted Supabase Edge Functions are deployed in production with this fork, outside the CI matrix. Standalone Deno 2 is unverified. Bun is best effort, without CI coverage. Cloudflare Workers has a known socket-close rejection ([#1196](https://github.com/porsager/postgres/issues/1196), [#1202](https://github.com/porsager/postgres/issues/1202)).
-await sql`CREATE TABLE IF NOT EXISTS camel_case (a_test INTEGER, b_test TEXT)`
-await sql`INSERT INTO camel_case ${ sql([{ aTest: 1, bTest: 1 }]) }`
-const data = await sql`SELECT ${ sql('aTest', 'bTest') } FROM camel_case`
+## Why this fork
-console.log(data) // [ { aTest: 1, bTest: '1' } ]
-```
+As many of my deployments are on serverless, I ran into some Postgres.js limitations that made it harder to use it reliably. I moved a couple of projects off it and patched others to compare the pros and cons.
-To only perform half of the transformation (eg. only the transformation **to** or **from** camel case), use the other transformation functions:
+But I also realised that even for a small team of one, there is a clear path to updating and fixing Postgres.js, and I decided to bring those changes, whether from local patches, parked issues or PRs, to the benefit of the wider community.
-```js
-// Transform the column names only to camel case
-// (for the results that are returned from the query)
-postgres({ transform: postgres.toCamel })
+The aim of this fork is to move faster while keeping rigorous review, automate broader, tedious testing, welcome community contributions, and make a library I enjoy using work better for everyone.
-await sql`CREATE TABLE IF NOT EXISTS camel_case (a_test INTEGER)`
-await sql`INSERT INTO camel_case ${ sql([{ a_test: 1 }]) }`
-const data = await sql`SELECT a_test FROM camel_case`
+### Fixed Postgres.js issues
-console.log(data) // [ { aTest: 1 } ]
-```
-```js
-// Transform the column names only from camel case
-// (for interpolated inserts, updates, and selects)
-const sql = postgres({ transform: postgres.fromCamel })
-await sql`CREATE TABLE IF NOT EXISTS camel_case (a_test INTEGER)`
-await sql`INSERT INTO camel_case ${ sql([{ aTest: 1 }]) }`
-const data = await sql`SELECT ${ sql('aTest') } FROM camel_case`
-console.log(data) // [ { a_test: 1 } ]
-```
-> Note that Postgres.js does not rewrite the static parts of the tagged template strings. So to transform column names in your queries, the `sql()` helper must be used - eg. `${ sql('columnName') }` as in the examples above.
-### Transform `undefined` Values
-By default, Postgres.js will throw the error `UNDEFINED_VALUE: Undefined values are not allowed` when undefined values are passed
-```js
-// Transform the column names to and from camel case
-const sql = postgres({
-  transform: {
-    undefined: null
-  }
-})
-await sql`CREATE TABLE IF NOT EXISTS transform_undefined (a_test INTEGER)`
-await sql`INSERT INTO transform_undefined ${ sql([{ a_test: undefined }]) }`
-const data = await sql`SELECT a_test FROM transform_undefined`
-console.log(data) // [ { a_test: null } ]
-```
-To combine with the built in transform functions, spread the transform in the `transform` object:
-```js
-// Transform the column names to and from camel case
-const sql = postgres({
-  transform: {
-    ...postgres.camel,
-    undefined: null
-  }
-})
-await sql`CREATE TABLE IF NOT EXISTS transform_undefined (a_test INTEGER)`
-await sql`INSERT INTO transform_undefined ${ sql([{ aTest: undefined }]) }`
-const data = await sql`SELECT ${ sql('aTest') } FROM transform_undefined`
-console.log(data) // [ { aTest: null } ]
-```
-### Custom Transform Functions
-To specify your own transformation functions, you can use the `column`, `value` and `row` options inside of `transform`, each an object possibly including `to` and `from` keys:
-* `to`: The function to transform the outgoing query column name to, i.e `SELECT ${ sql('aName') }` to `SELECT a_name` when using `postgres.toCamel`.
-* `from`: The function to transform the incoming query result column name to, see example below.
-> Both parameters are optional, if not provided, the default transformation function will be used.
-```js
-// Implement your own functions, look at postgres.toCamel, etc
-// as a reference:
-// https://github.com/porsager/postgres/blob/4241824ffd7aa94ffb482e54ca9f585d9d0a4eea/src/types.js#L310-L328
-function transformColumnToDatabase() { /* ... */ }
-function transformColumnFromDatabase() { /* ... */ }
-const sql = postgres({
-  transform: {
-    column: {
-      to: transformColumnToDatabase,
-      from: transformColumnFromDatabase,
-    },
-    value: { /* ... */ },
-    row: { /* ... */ }
-  }
-})
-```
-## Listen & notify
-When you call `.listen`, a dedicated connection will be created to ensure that you receive notifications instantly. This connection will be used for any further calls to `.listen`. The connection will automatically reconnect according to a backoff reconnection pattern to not overload the database server.
-### Listen `await sql.listen(channel, onnotify, [onlisten]) -> { state }`
-`.listen` takes the channel name, a function to handle each notify, and an optional function to run every time listen is registered and ready (happens on initial connect and reconnects). It returns a promise which resolves once the `LISTEN` query to Postgres completes, or if there is already a listener active. If either function throws, the error is rethrown as an uncaught exception, and the other listeners and the returned promise are not affected.
-```js
-await sql.listen('news', payload => {
-  const json = JSON.parse(payload)
-  console.log(json.this) // logs 'is'
-})
-```
-The optional `onlisten` method is great to use for a very simply queue mechanism:
-```js
-await sql.listen(
-  'jobs',
-  (x) => run(JSON.parse(x)),
-  ( ) => sql`select unfinished_jobs()`.forEach(run)
-)
-function run(job) {
-  // And here you do the work you please
-}
-```
-### Notify `await sql.notify(channel, payload) -> Result[]`
-Notify can be done as usual in SQL, or by using the `sql.notify` method.
-```js
-sql.notify('news', JSON.stringify({ no: 'this', is: 'news' }))
-```
-## Realtime subscribe
-Postgres.js implements the logical replication protocol of PostgreSQL to support subscription to real-time updates of `insert`, `update` and `delete` operations.
-> **NOTE** To make this work you must [create the proper publications in your database](https://www.postgresql.org/docs/current/sql-createpublication.html), enable logical replication by setting `wal_level = logical` in `postgresql.conf` and connect using either a replication or superuser.
-### Quick start
-#### Create a publication (eg. in migration)
-```sql
-CREATE PUBLICATION alltables FOR ALL TABLES
-```
-#### Subscribe to updates
-```js
-const sql = postgres({ publications: 'alltables' })
-const { unsubscribe } = await sql.subscribe(
-  'insert:events',
-  (row, { command, relation, key, old }) => {
-    // Callback function for each row change
-    // tell about new event row over eg. websockets or do something else
-  },
-  () => {
-    // Callback on initial connect and potential reconnects
-  },
-  (error) => {
-    // Callback on connection errors and changes that could not be decoded
-  }
-)
-```
-If any of these callbacks throws, the error is rethrown as an uncaught exception, and other subscribers and the replication stream are not affected.
-`onerror` is called with errors of the replication connection, after which the subscription reconnects on a new replication slot and calls `onsubscribe` again (these are also logged with `console.error`, and changes committed while it was disconnected are not delivered; if the reconnect itself fails, it is retried with backoff, its error is logged with `console.error` and passed to `onerror`, and it never ends the process), and with errors thrown while a change is decoded by a [transform](#data-transformation) or a custom type parser. Such a change is skipped, and the replication stream and later changes carry on. A decode error goes only to the subscriptions that would have received the change, matched by operation and table; a subscription filtered by key gets every skipped change of its table, as the key is read from the decoded row, even if the table has no primary key. If a column name transform throws, each change of that table is skipped and reported until the server describes the table again, for example after `ALTER TABLE`. If one of the matching subscriptions has no `onerror`, the error is rethrown once as an uncaught exception, which ends the process under Node's default handling. `onerror` stays registered across reconnects until `unsubscribe()`.
-### Subscribe pattern
-You can subscribe to specific operations, tables, or even rows with primary keys.
-#### `operation`      `:` `schema` `.` `table` `=` `primary_key`
-**`operation`** is one of ``` * | insert | update | delete ``` and defaults to `*`
-**`schema`** defaults to `public`
-**`table`** is a specific table name and defaults to `*`
-**`primary_key`** can be used to only subscribe to specific rows
-### Examples
-```js
-sql.subscribe('*',                () => /* everything */ )
-sql.subscribe('insert',           () => /* all inserts */ )
-sql.subscribe('*:users',          () => /* all operations on the public.users table */ )
-sql.subscribe('delete:users',     () => /* all deletes on the public.users table */ )
-sql.subscribe('update:users=1',   () => /* all updates on the users row with a primary key = 1 */ )
-```
-## Numbers, bigint, numeric
-`Number` in javascript is only able to represent 2<sup>53</sup>-1 safely which means that types in PostgreSQLs like `bigint` and `numeric` won't fit into `Number`.
-Since Node.js v10.4 we can use [`BigInt`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt) to match the PostgreSQL type `bigint` which is returned for eg. `count(*)`. Unfortunately, it doesn't work with `JSON.stringify` out of the box, so Postgres.js will return it as a string.
-If you want to use `BigInt` you can add this custom type:
-```js
-const sql = postgres({
-  types: {
-    bigint: postgres.BigInt
-  }
-})
-```
-There is currently no guaranteed way to handle `numeric` / `decimal` types in native Javascript. **These [and similar] types will be returned as a `string`**. The best way in this case is to use  [custom types](#custom-types).
-## Parameter types
-A `$1` placeholder has a type that PostgreSQL infers from the SQL around it (the column it is compared to or inserted into, a function argument, a cast). Postgres.js has to turn each JavaScript value into text for that type, and `parameter_types` chooses how.
-Some values carry a type Postgres.js can tell from the JavaScript value: `Date`, `Buffer` / `Uint8Array`, booleans, `bigint`, and anything wrapped in `sql.typed(value, oid)`, `sql.types.*`, `sql.json` or `sql.array` with elements. They are serialized for that type and sent in a single round trip, in every mode. Everything else (strings, numbers, plain objects, `sql.typed(value)` without an OID, an empty `sql.array([])`, arrays) has no such type. `null` is always SQL `NULL`.
-### `parameter_types: 'server'` (default)
-For a value whose type Postgres.js cannot tell, it first asks PostgreSQL for the type of the placeholder, which costs an extra round trip on every query with `prepare: false` and the first time each connection runs that SQL with `prepare: true`, and then serializes the value for that type. This has consequences worth knowing:
-- a string sent to a `json` or `jsonb` placeholder is sent as JSON, so `'{"a":1}'` is stored as a JSON string, not an object
-- a string or number sent to a `date`, `timestamp` or `timestamptz` placeholder goes through `new Date(x).toISOString()`, where a date-only string such as `'2020-01-02'` is read as UTC and a date-and-time string without an offset such as `'2020-01-02T10:00'` is read in the Node.js process time zone (`TZ`)
-- anything other than `true` sent to a `boolean` placeholder is stored as `false`, including the strings `'true'` and `'t'` and the number `1`
-- a string sent to a `bytea` placeholder is sent as hex of its UTF-8 bytes
-- a custom type registered in `types` with a `from` list runs its `serialize` function
-### `parameter_types: 'client'`
-The JavaScript value decides how it is serialized and PostgreSQL parses the text, so a query with values is one round trip:
-- a string is sent unchanged as text
-- a number is sent as its JavaScript text (`'' + n`)
-- a plain object (prototype `Object.prototype` or `null`) is sent as `JSON.stringify(x)`
-- any other object (Decimal, Luxon, moment, URL, class instances) is sent as `'' + x`
-- `null` is SQL `NULL`; `undefined` is handled as before
-- a value with a type Postgres.js can tell from the JavaScript value is serialized for that type, as with `'server'`
-- an array whose elements have no such type still makes Postgres.js ask PostgreSQL for the placeholder's type first, because only PostgreSQL knows whether the placeholder is an array, JSON or a custom type; that query takes the extra round trip
-What this changes compared to `'server'`:
-| Value | Type PostgreSQL infers for the placeholder | `'server'` | `'client'` |
-| --- | --- | --- | --- |
-| string | json, jsonb | sent as JSON: stores a JSON string | parsed as JSON; text that is not JSON is rejected |
-| string | boolean | always `false` | PostgreSQL boolean input (`'t'`, `'yes'`, `'on'`, `'1'` are true); invalid text is rejected |
-| string | date, timestamp, timestamptz | `new Date(s).toISOString()`: date-only strings are read as UTC, date-and-time strings without an offset in the Node.js process time zone (`TZ`) | parsed by PostgreSQL in the PostgreSQL session's `TimeZone` setting; `date` and `timestamp` ignore an explicit offset |
-| string | bytea | hex of the UTF-8 bytes | bytea text input; differs only for strings containing backslashes |
-| string, number | a custom type registered in `types` with a `from` list | the type's `serialize` | sent unchanged as text |
-| number | json, jsonb | `JSON.stringify` (`NaN` and `Infinity` become `null`) | the number's text (`NaN` and `Infinity` are rejected) |
-| number | boolean | `false` | `1` is true, `0` is false, anything else is rejected |
-| number | date, timestamp, timestamptz | `new Date(ms)` | rejected, except `Infinity`; a 6- or 8-digit number is read as a `YYMMDD` or `YYYYMMDD` date |
-| plain object | json, jsonb | `JSON.stringify` or your json `serialize` | `JSON.stringify` |
-| plain object | text | `[object Object]` | JSON text |
-| plain object | a custom type registered in `types` with a `from` list | the type's `serialize` | JSON text, normally rejected |
-| class instance | json, jsonb | `JSON.stringify`, so `toJSON` applies | `'' + x` |
-| class instance | date, timestamp, timestamptz | `new Date(x)` | `'' + x`, normally rejected |
-`time`, `timetz` and `interval` placeholders have no serializer in either mode: strings and numbers are sent unchanged as text.
-In practice:
-- pass `new Date(ms)` for epoch numbers, and set `connection: { timezone }` so date strings are read in the time zone you expect
-- pass `sql.json(s)` for a JSON string value, and `sql.types.name(v)` or `sql.typed(v, oid)` for a custom type; a custom type's `serialize` also runs for a whole array bound to that type, never for a plain value
-- `NaN`, `Infinity` and `-0` are sent as `NaN`, `Infinity` and `0`, and PostgreSQL's input rules for the placeholder's type decide
-Run `'warn'` first to see which of your queries are affected.
-**Planned for 5.0:** `'client'` becomes the default. Pass `parameter_types: 'server'` to keep the 4.x behaviour.
-### `parameter_types: 'warn'`
-`'warn'` behaves exactly like `'server'`, and also reports every query in which a value would be sent differently by `'client'`. The report goes to `ontypemismatch`, or to `console.warn` when it is not set:
-```js
-const sql = postgres({
-  parameter_types: 'warn',
-  ontypemismatch: ({ query, parameters }) => {
-    // parameters: [{ position: 2, oid: 3802, typeof: 'string' }]
-    // position is the $n number, oid the type PostgreSQL inferred for the placeholder
-  }
-})
-```
-With `debug: true` each entry also carries `serverText` and `clientText`, the two texts that were compared; `clientText` is the error when the `'client'` mode would throw. A query is reported on every execution that has a difference; sample in `ontypemismatch` if that is too much. `'warn'` serializes each untyped value twice and compares the strings. The option can also be set with `?parameter_types=warn` in the connection URL or `PGPARAMETER_TYPES`.
-`'warn'` compares the serialized text, not the stored value, so a report does not always mean the stored value would change.
-These reported cases store the same value under both modes:
-- `0`, `'0'`, `'false'`, `'no'` and `'off'` sent to a `boolean` placeholder (the texts differ, both store `false`)
-- a date string with an explicit offset sent to a `timestamptz` placeholder, as long as it has no more than millisecond precision (`toISOString()` truncates microseconds, so a string with microseconds stores a different value under `'server'`)
-- a string without backslashes sent to a `bytea` placeholder
-These reported cases store a different value, or are rejected, under `'client'`:
-- `1`, `'t'`, `'true'`, `'yes'`, `'on'` and `'1'` sent to a `boolean` placeholder (stored `false` today, `true` under `'client'`)
-- a date string with an explicit offset sent to a `timestamp` or `date` placeholder (`'server'` converts to UTC first, `'client'` drops the offset)
-- a string sent to a `json` or `jsonb` placeholder, a plain object sent to a `text` placeholder, and a number sent to a date, timestamp or boolean placeholder
-- a string or number sent to a custom type registered in `types` with a `from` list, which skips its `serialize`
-Date strings without an explicit offset:
-| String | Placeholder | Stored the same under both modes when |
-| --- | --- | --- |
-| date and time, such as `'2020-01-02T10:00'` | `timestamptz` | the Node.js process time zone and the PostgreSQL session's `TimeZone` setting match |
-| date only, such as `'2020-01-02'` | `timestamptz` | the PostgreSQL session's `TimeZone` setting is UTC |
-| date and time | `timestamp` or `date` | the Node.js process runs in UTC (`'server'` stores the UTC wall time, `'client'` stores the text as written) |
-## Result Array
-The `Result` Array returned from queries is a custom array allowing for easy destructuring or passing on directly to JSON.stringify or general Array usage. It includes the following properties.
-### .count
-The `count` property is the number of affected rows returned by the database. This is useful for insert, update and delete operations to know the number of rows since .length will be 0 in these cases if not using `RETURNING ...`.
-### .command
-The `command` run by the query - eg. one of `SELECT`, `UPDATE`, `INSERT`, `DELETE`
-### .columns
-The `columns` returned by the query useful to determine types, or map to the result values when using `.values()`
-```js
-{
-  name  : String,    // Column name,
-  type  : oid,       // PostgreSQL oid column type
-  parser: Function   // The function used by Postgres.js for parsing
-}
-```
-### .statement
-The `statement` contains information about the statement implicitly created by Postgres.js.
-```js
-{
-  name    : String,  // The auto generated statement name
-  string  : String,  // The actual query string executed
-  types   : [oid],   // An array of oid expected as input parameters
-  columns : [Column] // Array of columns - same as Result.columns
-}
-```
-### .state
-This is the state `{ pid, secret }` of the connection that executed the query.
-## Connection details
-### All Postgres options
-```js
-const sql = postgres('postgres://username:password@host:port/database', {
-  host                 : '',            // Postgres ip address[es] or domain name[s]
-  port                 : 5432,          // Postgres server port[s]
-  path                 : '',            // unix socket path (usually '/tmp')
-  database             : '',            // Name of database to connect to
-  username             : '',            // Username of database user
-  password             : '',            // Password of database user
-  ssl                  : false,         // true, prefer, require, tls.connect options
-  sslnegotiation       : null,          // direct
-  max                  : 10,            // Max number of connections
-  max_lifetime         : null,          // Max lifetime in seconds (more info below)
-  idle_timeout         : 0,             // Idle connection timeout in seconds
-  connect_timeout      : 30,            // Connect timeout in seconds
-  prepare              : true,          // Automatic creation of prepared statements
-  types                : [],            // Array of custom types, see more below
-  onnotice             : fn,            // Default console.log, set false to silence NOTICE
-  onparameter          : fn,            // (key, value) when server param change
-  onidle               : fn,            // (connId) when a connection returns to the pool idle
-  debug                : fn,            // Is called with (connection, query, params, types)
-  socket               : fn,            // fn returning custom socket to use
-  transform            : {
-    undefined          : undefined,     // Transforms undefined values (eg. to null)
-    column             : fn,            // Transforms incoming column names
-    value              : fn,            // Transforms incoming row values
-    row                : fn             // Transforms entire rows
-  },
-  connection           : {
-    application_name   : 'postgres.js', // Default application_name
-    ...                                 // Other connection parameters, see https://www.postgresql.org/docs/current/runtime-config-client.html
-  },
-  target_session_attrs : null,          // Use 'read-write' with multiple hosts to
-                                        // ensure only connecting to primary
-  fetch_types          : true,          // Automatically fetches types on connect
-                                        // on initial connection.
-  parameter_types      : 'server',      // 'client' or 'warn', see Parameter types (PGPARAMETER_TYPES)
-  ontypemismatch       : fn,            // Called by parameter_types: 'warn', default console.warn
-})
-```
-The `onnotice`, `onparameter`, `ontypemismatch`, `onnotify`, `onclose`, `onidle` and `debug` callbacks passed in the options are called synchronously from inside the driver. If one throws, the error is rethrown as an uncaught exception and the connection and its queries are not affected; under Node's default handling that ends the process.
-Note that `max_lifetime = 60 * (30 + Math.random() * 30)` by default. This resolves to an interval between 30 and 60 minutes to optimize for the benefits of prepared statements **and** working nicely with Linux's OOM killer.
-### Dynamic passwords
-When clients need to use alternative authentication schemes such as access tokens or connections to databases with rotating passwords, provide either a synchronous or asynchronous function that will resolve the dynamic password value at connection time.
-```js
-const sql = postgres(url, {
-  // Other connection config
-  ...
-  // Password function for the database user
-  password : async () => await signer.getAuthToken(),
-})
-```
-### SSL
-Although [vulnerable to MITM attacks](https://security.stackexchange.com/a/229297/174913), a common configuration for the `ssl` option for some cloud providers is to set `rejectUnauthorized` to `false` (if `NODE_ENV` is `production`):
-```js
-const sql =
-  process.env.NODE_ENV === 'production'
-    ? // "Unless you're using a Private or Shield Heroku Postgres database, Heroku Postgres does not currently support verifiable certificates"
-      // https://help.heroku.com/3DELT3RK/why-can-t-my-third-party-utility-connect-to-heroku-postgres-with-ssl
-      postgres({ ssl: { rejectUnauthorized: false } })
-    : postgres()
-```
-For more information regarding `ssl` with `postgres`, check out the [Node.js documentation for tls](https://nodejs.org/dist/latest-v16.x/docs/api/tls.html#new-tlstlssocketsocket-options).
-### Multi-host connections - High Availability (HA)
-Multiple connection strings can be passed to `postgres()` in the form of `postgres('postgres://localhost:5432,localhost:5433', ...)`. This works the same as native the `psql` command. Read more at [multiple host URIs](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-MULTIPLE-HOSTS).
-Connections will be attempted in order of the specified hosts/ports. On a successful connection, all retries will be reset. This ensures that hosts can come up and down seamlessly.
-If you specify `target_session_attrs: 'primary'` or `PGTARGETSESSIONATTRS=primary` Postgres.js will only connect to the primary host, allowing for zero downtime failovers.
-### The Connection Pool
-Connections are created lazily once a query is created. This means that simply doing const `sql = postgres(...)` won't have any effect other than instantiating a new `sql` instance.
-> No connection will be made until a query is made.
-For example:
-```js
-const sql = postgres() // no connections are opened
-await sql`...` // one connection is now opened
-await sql`...` // previous opened connection is reused
-// two connections are opened now
-await Promise.all([
-  sql`...`,
-  sql`...`
-])
-```
-> When there are high amount of concurrent queries, `postgres` will open as many connections as needed up until `max` number of connections is reached. By default `max` is 10. This can be changed by setting `max` in the `postgres()` call. Example - `postgres('connectionURL', { max: 20 })`.
-This means that we get a much simpler story for error handling and reconnections. Queries will be sent over the wire immediately on the next available connection in the pool. Connections are automatically taken out of the pool if you start a transaction using `sql.begin()`, and automatically returned to the pool once your transaction is done.
-Any query which was already sent over the wire will be rejected if the connection is lost. It'll automatically defer to the error handling you have for that query, and since connections are lazy it'll automatically try to reconnect the next time a query is made. The benefit of this is no weird generic "onerror" handler that tries to get things back to normal, and also simpler application code since you don't have to handle errors out of context.
-There are no guarantees about queries executing in order unless using a transaction with `sql.begin()` or setting `max: 1`. Of course doing a series of queries, one awaiting the other will work as expected, but that's just due to the nature of js async/promise handling, so it's not necessary for this library to be concerned with ordering.
-Since this library automatically creates prepared statements, it also has a default max lifetime for connections to prevent memory bloat on the database itself. This is a random interval for each connection between 45 and 90 minutes. This allows multiple connections to independently come up and down without affecting the service.
-### Pool stats
-`sql.stats()` returns a snapshot of the pool as a plain object, ready to log, serialise from a health endpoint or map to metrics gauges:
-```js
-sql.stats()
-// { max: 10, totalCount: 7, idleCount: 2, waitingCount: 3,
-//   activeCount: 4, availableCount: 5,
-//   busyCount: 3, reservedCount: 1, connectingCount: 1, closingCount: 0,
-//   executingCount: 4, listenCount: 1, subscribeCount: 0 }
-```
-| Field | Meaning |
-|---|---|
-| `max` | The `max` option |
-| `totalCount` | Connections that exist: connecting, idle or in use |
-| `idleCount` | Connections with a live session that are not in use. A connection released while its reserved handle still has queries in flight is idle with `executingCount` above 0 |
-| `waitingCount` | Issued queries and `reserve()` or `begin()` calls that are not running yet: those in the pool queue, those held by a connection that is still opening, those pipelined behind a connection's running query, and those a reserved handle or transaction has queued behind its own connection |
-| `activeCount` | `busyCount + reservedCount`, connections in use |
-| `availableCount` | `idleCount` plus the slots the pool can still open (`max - totalCount - closingCount`): connections a query can get without waiting behind other work |
-| `busyCount` | Pool connections running queries, including connections at the pipeline limit |
-| `reservedCount` | Connections held by `reserve()` or `begin()` |
-| `connectingCount` | Connections opening a session |
-| `closingCount` | Connections draining or closing. They are not in `totalCount`, but still hold a pool slot until closed |
-| `executingCount` | Queries the server is running right now, at most one per connection, on pool and reserved connections alike. It includes the queries the driver runs while a connection starts, and a `COPY` for its whole duration |
-| `listenCount` | Connections held by the internal `sql.listen()` pool (0 or 1) |
-| `subscribeCount` | Connections held by the internal `sql.subscribe()` pool (0 or 1) |
-`totalCount` and `idleCount` have the same meaning as in node-postgres. `waitingCount` is node-postgres's `waitingCount` extended to queries pipelined on connections and queued in leases, and it includes queries sent with `sql` directly, as `pool.query()` does there. Once the pool is at `max`, Postgres.js pipelines new queries onto busy connections, so waiting work can sit on a connection rather than in the pool queue; `waitingCount` counts it too, so `executingCount + waitingCount` covers all issued work that has not finished. Every snapshot satisfies `totalCount === idleCount + busyCount + reservedCount + connectingCount` and `totalCount + closingCount <= max`, the remainder being slots the pool has not opened.
-`listenCount` and `subscribeCount` are counted outside `max`, and the other fields only describe the `max` pool connections. A reserved connection's `stats()` returns the same snapshot, but `sql` inside `sql.begin()` and savepoints has no `stats()`, so call it on the main `sql`.
-The pool is saturated when `waitingCount > 0 && availableCount === 0`: every connection is in use and more work is waiting. Saturation alone is not a reason to fail a health check, because a single pipelined query on a fully used pool, including a transaction pipelining its own statements, is enough to meet it. A health endpoint should compare `waitingCount` against a limit the application chooses:
-```js
-import http from 'node:http'
-const MAX_WAITING = 100
-http.createServer((req, res) => {
-  const stats = sql.stats()
-  const overloaded = stats.availableCount === 0 && stats.waitingCount > MAX_WAITING
-  res.writeHead(overloaded ? 503 : 200, { 'content-type': 'application/json' })
-  res.end(JSON.stringify(stats))
-}).listen(8080)
-```
-How much waiting work is acceptable depends on the query durations and the latency the application can tolerate, so the limit has no universal value.
-Change events and a running total of finished queries are planned together with the diagnostics events, so for now take snapshots on a timer or on request.
-### Connection timeout
-By default, connections will not close until `.end()` is called. However, it may be useful to have them close automatically when:
-- re-instantiating multiple ` sql`` ` instances
-- using Postgres.js in a Serverless environment (Lambda, etc.)
-- using Postgres.js with a database service that automatically closes connections after some time (see [`ECONNRESET` issue](https://github.com/porsager/postgres/issues/179))
-This can be done using the `idle_timeout` or `max_lifetime` options. These configuration options specify the number of seconds to wait before automatically closing an idle connection and the maximum time a connection can exist, respectively. Both are also checked when an idle connection is handed out, so an idle connection that is past either limit (for example after a serverless instance was frozen) is closed instead of being used.
-For example, to close a connection that has either been idle for 20 seconds or existed for more than 30 minutes:
-```js
-const sql = postgres({
-  idle_timeout: 20,
-  max_lifetime: 60 * 30
-})
-```
-### Vercel Fluid Compute
-On Vercel's Fluid Compute an instance can be suspended while a connection sits idle and before `idle_timeout` has closed it, which leaves the connection open on the server. `attachDatabasePool` from `@vercel/functions` keeps the instance alive until idle connections have closed. Pass it the pool through `vercelPool`:
-```js
-import postgres from '@steadybrew/postgresjs'
-import { vercelPool } from '@steadybrew/postgresjs/vercel'
-import { attachDatabasePool } from '@vercel/functions'
-const sql = postgres({ idle_timeout: 5 })
-attachDatabasePool(vercelPool(sql))
-```
-`vercelPool` requires `idle_timeout` to be a number of seconds. It hooks into the `onidle` option, which is called with the connection id each time a connection returns to the pool idle and its idle timer starts, and it keeps any `onidle` you set yourself. If `onidle` throws, the error is rethrown as an uncaught exception and the connection is not affected. A connection that was frozen past `idle_timeout` anyway is closed when it is next handed out (see [Connection timeout](#connection-timeout)).
-### Cloudflare Workers support
-Postgres.js has built-in support for the [TCP socket API](https://developers.cloudflare.com/workers/runtime-apis/tcp-sockets/) in Cloudflare Workers, which is [on-track](https://github.com/wintercg/proposal-sockets-api) to be standardized and adopted in Node.js and other JavaScript runtimes, such as Deno.
-You can use Postgres.js directly in a Worker, or to benefit from connection pooling and query caching, via the [Hyperdrive](https://developers.cloudflare.com/hyperdrive/learning/connect-to-postgres/#driver-examples) service available to Workers by passing the Hyperdrive `connectionString` when creating a new `postgres` client as follows:
-```ts
-// Requires Postgres.js 3.4.0 or later
-import postgres from '@steadybrew/postgresjs'
-interface Env {
-    HYPERDRIVE: Hyperdrive;
-}
-export default async fetch(req: Request, env: Env, ctx: ExecutionContext) {
-    // The Postgres.js library accepts a connection string directly
-    const sql = postgres(env.HYPERDRIVE.connectionString)
-    const results = await sql`SELECT * FROM users LIMIT 10`
-    return Response.json(results)
-}
-```
-In `wrangler.toml` you will need to enable the `nodejs_compat` compatibility flag to allow Postgres.js to operate in the Workers environment:
-```toml
-compatibility_flags = ["nodejs_compat"]
-```
-### Auto fetching of array types
-Postgres.js automatically fetches array-type information when each connection initializes.
-If you have revoked access to `pg_catalog` this feature will no longer work and will need to be disabled.
-You can disable catalog discovery by setting `fetch_types` to `false`. A fixed set of 22 common built-in array types still supports parsing and serialization, including text, numeric, boolean, JSON, date, UUID, and byte arrays. This changes earlier `fetch_types: false` behavior, which returned built-in arrays as raw strings. Other built-in, user-defined, and extension arrays still require discovery or explicit type handlers.
-SQL `NULL` elements are returned as JavaScript `null`; a quoted text element `"NULL"` remains a string. Explicit array parsers and serializers are preserved independently. Catalog discovery with `fetch_types: true` remains per connection; this change does not cache catalog metadata.
-Column, value, and row transforms apply to application query results; initialization metadata retains its original shape.
-### Environmental variables
-It is also possible to connect to the database without a connection string or any options. Postgres.js will fall back to the common environment variables used by `psql` as in the table below:
-```js
-const sql = postgres()
-```
-| Option             | Environment Variables    |
-| ------------------ | ------------------------ |
-| `host`             | `PGHOST`                 |
-| `port`             | `PGPORT`                 |
-| `database`         | `PGDATABASE`             |
-| `username`         | `PGUSERNAME` or `PGUSER` |
-| `password`         | `PGPASSWORD`             |
-| `application_name` | `PGAPPNAME`              |
-| `idle_timeout`     | `PGIDLE_TIMEOUT`         |
-| `connect_timeout`  | `PGCONNECT_TIMEOUT`      |
-| `parameter_types`  | `PGPARAMETER_TYPES`      |
-### Prepared statements
-Prepared statements will automatically be created for any queries where it can be inferred that the query is static. This can be disabled by using the `prepare: false` option. For instance — this is useful when [using PGBouncer in `transaction mode`](https://github.com/porsager/postgres/issues/93#issuecomment-656290493).
-With `prepare: false`, `parameter_types: 'client'` sends queries with values in one round trip, unless a value is an untyped array; see [Parameter types](#parameter-types).
-**update**: [since 1.21.0](https://www.pgbouncer.org/2023/10/pgbouncer-1-21-0)
-PGBouncer supports protocol-level named prepared statements when [configured
-properly](https://www.pgbouncer.org/config.html#max_prepared_statements)
-## Custom Types
-You can add ergonomic support for custom types, or simply use `sql.typed(value, type)` inline, where type is the PostgreSQL `oid` for the type and the correctly serialized string. _(`oid` values for types can be found in the `pg_catalog.pg_type` table.)_
-Adding Query helpers is the cleanest approach which can be done like this:
-```js
-const sql = postgres({
-  types: {
-    rect: {
-      // The pg_types oid to pass to the db along with the serialized value.
-      to        : 1337,
-      // An array of pg_types oids to handle when parsing values coming from the db.
-      from      : [1337],
-      //Function that transform values before sending them to the db.
-      serialize : ({ x, y, width, height }) => [x, y, width, height],
-      // Function that transforms values coming from the db.
-      parse     : ([x, y, width, height]) => { x, y, width, height }
-    }
-  }
-})
-// Now you can use sql.typed.rect() as specified above
-const [custom] = await sql`
-  insert into rectangles (
-    name,
-    rect
-  ) values (
-    'wat',
-    ${ sql.typed.rect({ x: 13, y: 37, width: 42, height: 80 }) }
-  )
-  returning *
-`
-// custom = { name: 'wat', rect: { x: 13, y: 37, width: 42, height: 80 } }
-```
-With `parameter_types: 'client'` a type's `serialize` runs for `sql.typed.name(v)` and for a whole array bound to that type, not for a plain value; see [Parameter types](#parameter-types).
-### Custom socket
-Easily do in-process ssh tunneling to your database by providing a custom socket for Postgres.js to use. The function (optionally async) must return a socket-like duplex stream.
-Here's a sample using [ssh2](https://github.com/mscdex/ssh2)
-```js
-import ssh2 from 'ssh2'
-const sql = postgres({
-  ...options,
-  socket: ({ host: [host], port: [port] }) => new Promise((resolve, reject) => {
-    const ssh = new ssh2.Client()
-    ssh
-    .on('error', reject)
-    .on('ready', () =>
-      ssh.forwardOut('127.0.0.1', 12345, host, port,
-        (err, socket) => err ? reject(err) : resolve(socket)
-      )
-    )
-    .connect(sshOptions)
-  })
-})
-```
-## Teardown / Cleanup
-To ensure proper teardown and cleanup on server restarts use `await sql.end()` before `process.exit()`.
-Calling `sql.end()` will reject new queries and return a Promise which resolves when all queries are finished and the underlying connections are closed. If a `{ timeout }` option is provided any pending queries will be rejected once the timeout (in seconds) is reached and the connections will be destroyed.
-With explicit resource management the pool ends itself at the end of a scope:
-```js
-async function main() {
-  await using sql = postgres()
-  await sql`select 1`
-}
-```
-This calls `sql.end()` when the scope exits, so it suits scripts and jobs, not a shared client at a module's top level. The syntax needs Node.js 24+ or TypeScript 5.2+.
-#### Sample shutdown using [Prexit](https://github.com/porsager/prexit)
-```js
-import prexit from 'prexit'
-prexit(async () => {
-  await sql.end({ timeout: 5 })
-  await new Promise(r => server.close(r))
-})
-```
-## Reserving connections
-### `await sql.reserve()`
-The `reserve` method pulls out a connection from the pool, and returns a client that wraps the single connection. This can be used for running queries on an isolated connection.
-```ts
-const reserved = await sql.reserve()
-await reserved`select * from users`
-await reserved.release()
-```
-### `reserved.release()`
-Once you have finished with the reserved connection, call `release` to add it back to the pool.
-```js
-using reserved = await sql.reserve()
-await reserved`select * from users`
-```
-A `using` or `await using` declaration calls `release()` when the scope exits.
-After release, queries through that reserved handle reject with `CONNECTION_ENDED`. Call `sql.reserve()` again to acquire a new handle. A reserved handle whose connection has closed cannot be reused after reconnect.
-## Error handling
-Errors are all thrown to related queries and never globally. Errors coming from database itself are always in the [native Postgres format](https://www.postgresql.org/docs/current/errcodes-appendix.html), and the same goes for any [Node.js errors](https://nodejs.org/api/errors.html#errors_common_system_errors) eg. coming from the underlying connection.
-Query errors will contain a stored error with the origin of the query to aid in tracing errors.
-Query errors will also contain the `query` string and the `parameters`. These are not enumerable to avoid accidentally leaking confidential information in logs. To log these it is required to specifically access `error.query` and `error.parameters`, or set `debug: true` in options.
-There are also the following errors specifically for this library.
-##### UNSAFE_TRANSACTION
-> Only use sql.begin or max: 1
-To ensure statements in a transaction runs on the same connection (which is required for them to run inside the transaction), you must use [`sql.begin(...)`](#transactions) or only allow a single connection in options (`max: 1`).
-##### UNDEFINED_VALUE
-> Undefined values are not allowed
-Postgres.js won't accept `undefined` as values in tagged template queries since it becomes ambiguous what to do with the value. If you want to set something to null, use `null` explicitly.
-##### MESSAGE_NOT_SUPPORTED
-> X (X) is not supported
-Whenever a message is received from Postgres which is not supported by this library. Feel free to file an issue if you think something is missing.
-##### MAX_PARAMETERS_EXCEEDED
-> Max number of parameters (65534) exceeded
-The postgres protocol doesn't allow more than 65534 (16bit) parameters. If you run into this issue there are various workarounds such as using `sql([...])` to escape values instead of passing them as parameters.
-##### SASL_SIGNATURE_MISMATCH
-> Message type X not supported
-When using SASL authentication the server responds with a signature at the end of the authentication flow which needs to match the one on the client. This is to avoid [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). If you receive this error the connection was canceled because the server did not reply with the expected signature.
-##### NOT_TAGGED_CALL
-> Query not called as a tagged template literal
-Making queries has to be done using the sql function as a [tagged template](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals#Tagged_templates). This is to ensure parameters are serialized and passed to Postgres as query parameters with correct types and to avoid SQL injection.
-##### SSL_NOT_SUPPORTED
-> The server does not support SSL connections
-The server answered the SSL request with a refusal while `ssl` is set to `require` (or another mode that does not fall back to plain text). The attempt fails at once for a single host. Use `ssl: 'prefer'` to fall back to an unencrypted connection, or enable SSL on the server.
-##### TARGET_SESSION_ATTRS
-> No host matched target_session_attrs=read-write: localhost:5432 is read-only
-No host satisfied [`target_session_attrs`](#connection-details). This error is the `cause` of the `CONNECTION_CLOSED` error the query rejects with, so retry logic keyed on `CONNECTION_CLOSED` keeps working; read `err.cause.code` and `err.cause.message` for the reason. The message names the requested value and each host with the reason it was rejected. With several hosts, the connection fails at once when every host answered and none matched; if any host failed for another reason (refused, closed, timed out), the client keeps retrying until `connect_timeout` instead, since a failover may be in progress. With a single host, the client keeps retrying until `connect_timeout` before failing, because a single endpoint that is read-only is often in the middle of a failover, for example a cluster DNS name that still points at the old primary.
-##### AUTH_TYPE_NOT_IMPLEMENTED
-> Auth type X not implemented
-Postgres supports many different authentication types. This one is not supported.
-##### CONNECTION_CLOSED
-> write CONNECTION_CLOSED host:port
-This error is thrown if the connection was closed, or could not be opened, without an error of its own. When the server or the network ended the session, or no host matched `target_session_attrs`, the underlying error is available as `err.cause`.
-##### CONNECTION_ENDED
-> write CONNECTION_ENDED host:port
-This error is thrown if the user has called [`sql.end()`](#teardown--cleanup) and performed a query afterward.
-A reserved `sql` used after `release()`, or a transaction `sql` used after `begin()` has committed, rolled back or prepared, also rejects with `CONNECTION_ENDED`.
-##### CONNECTION_DESTROYED
-> write CONNECTION_DESTROYED host:port
-This error is thrown for any queries that were pending when the timeout to [`sql.end({ timeout: X })`](#teardown--cleanup) was reached.
-##### CONNECT_TIMEOUT
-> write CONNECT_TIMEOUT host:port
-The timeout applies to each connection attempt and covers socket creation, TCP and TLS negotiation, authentication, session checks and type discovery. When an attempt times out, the next host is tried. The acquisition as a whole is bounded by `connect_timeout` multiplied by the number of hosts, measured from the first attempt; time spent waiting on an inherited reconnect delay is not counted. Set it with `connect_timeout` or `PGCONNECT_TIMEOUT` (30 seconds by default); zero disables both limits. The same value also bounds a graceful close: if the server does not close the socket within `connect_timeout` seconds after `end()` sends Terminate, the connection is closed anyway; zero leaves a graceful close unbounded.
-If the only attempt times out, the error is `CONNECT_TIMEOUT`. Once earlier attempts have failed, exhausting the overall budget reports the earlier error, such as the last server error or `CONNECTION_CLOSED`. With a single host, a socket or socket factory error rejects the query once; with several hosts, errors keep cycling through the hosts with backoff until the budget is spent. Queries already sent to the server are not replayed.
-##### COPY_IN_PROGRESS
-> You cannot execute queries during copy
-This error is thrown for a statement on a `sql.reserve()` or `sql.begin()` handle while its copy operation (writable / readable) runs, including statements sent before the server started it. A query, `sql.reserve()` or `sql.begin()` through `sql` gets it when every connection is running a copy operation whose writable has not been ended; otherwise it waits for a connection.
-##### TRANSACTION_ROLLED_BACK
-> The server rolled the transaction back instead of committing it
-This error is thrown by `sql.begin()` when the server answers the final `COMMIT` (or `PREPARE TRANSACTION`) with `ROLLBACK`, because the transaction was aborted by a statement whose error the callback did not surface, such as a failing query that was not awaited. Nothing was committed. When such a query's error was already recorded, it is the error's `cause`.
-## TypeScript support
-`postgres` has TypeScript support. You can pass a row list type for your queries in this way:
-```ts
-interface User {
-  id: number
-  name: string
-}
-const users = await sql<User[]>`SELECT * FROM users`
-users[0].id // ok => number
-users[1].name // ok => string
-users[0].invalid // fails: `invalid` does not exists on `User`
-```
-However, be sure to check the array length to avoid accessing properties of `undefined` rows:
-```ts
-const users = await sql<User[]>`SELECT * FROM users WHERE id = ${id}`
-if (!users.length)
-  throw new Error('Not found')
-return users[0]
-```
-You can also prefer destructuring when you only care about a fixed number of rows.
-In this case, we recommend you to prefer using tuples to handle `undefined` properly:
-```ts
-const [user]: [User?] = await sql`SELECT * FROM users WHERE id = ${id}`
-if (!user) // => User | undefined
-  throw new Error('Not found')
-return user // => User
-// NOTE:
-const [first, second]: [User?] = await sql`SELECT * FROM users WHERE id = ${id}` // fails: `second` does not exist on `[User?]`
-const [first, second] = await sql<[User?]>`SELECT * FROM users WHERE id = ${id}` // don't fail : `second: User | undefined`
-```
+- **Transactions keep their own connection.** Fixes connection reuse that could commit another transaction's unfinished writes or let a disconnected handle read another user's rows through RLS. [#1204](https://github.com/porsager/postgres/issues/1204), [#1216](https://github.com/porsager/postgres/issues/1216)
+- **Each query gets its own result.** Fixes pipelined queries receiving another query's rows or error, and results with empty slots after a failed query. [#1082](https://github.com/porsager/postgres/issues/1082), [#1252](https://github.com/porsager/postgres/issues/1252), [#1253](https://github.com/porsager/postgres/issues/1253)
+- **Rollbacks aren't reported as successful commits.** `sql.begin()` rejects when the server rolls back the commit. [#1217](https://github.com/porsager/postgres/issues/1217)
+- **Fewer hangs and crashes.** Fixes reservations and shutdown hanging after disconnects, queries stuck after a slow `COPY` reader, and closed transaction handles crashing the process. [#1195](https://github.com/porsager/postgres/issues/1195), [#1097](https://github.com/porsager/postgres/issues/1097), [#1016](https://github.com/porsager/postgres/pull/1016), [#1208](https://github.com/porsager/postgres/issues/1208)
+- **Recover after outages.** Failed connections [wait before retrying](docs/api.md#connection-timeout), avoiding a burst of simultaneous retries. With [multiple hosts](docs/api.md#multi-host-connections---high-availability-ha), the client tries another server and can wait for a writable primary.
-We do our best to type all the public API, however types are not always updated when features are added or changed. Feel free to open an issue if you have trouble with types.
+[50+ bug fixes and test coverage →](docs/fixed-issues.md)
-## Migration tools
+### Faster queries behind poolers
-Postgres.js doesn't come with any migration solution since it's way out of scope, but here are some modules that support Postgres.js for migrations:
+With `prepare: false`, parameterized queries can pay for an extra network round trip. The opt-in [`parameter_types: 'client'`](docs/api.md#parameter-types) removes it for supported values. In one production app behind the Supabase pooler, median query time fell from **5.3 ms to 3.1 ms** over a day on each mode. Results depend on your workload; p99 was unchanged. Use `'warn'` first to check for serialization differences.
-- https://github.com/porsager/postgres-shift
-- https://github.com/lukeed/ley
-- https://github.com/JAForbes/pgmg
+### New features
-## Thank you
+- **See pool pressure.** [`sql.stats()`](docs/api.md#pool-stats) reports busy and idle connections and waiting queries.
+- **Handle serverless suspension.** Expired idle connections are replaced on resume; the [Vercel Fluid Compute adapter](docs/api.md#vercel-fluid-compute) keeps instances alive until idle connections close.
+- **Automatic cleanup.** [`await using`](docs/api.md#teardown--cleanup) closes a pool and `using` releases a reserved connection when its scope ends. Requires Node.js 24+ or TypeScript 5.2+.
+- **Arrays without startup discovery.** With [`fetch_types: false`](docs/api.md#auto-fetching-of-array-types), common built-in arrays still parse and serialize without a catalog query.
-A really big thank you to [@JAForbes](https://twitter.com/jmsfbs) who introduced me to Postgres and still holds my hand navigating all the great opportunities we have.
+## Documentation
-Thanks to [@ACXgit](https://twitter.com/andreacoiutti) for initial tests and dogfooding.
+- [API reference](docs/api.md) — queries, transactions, types, options and errors. Also shipped in the npm package at `docs/api.md` for editors and code assistants.
+- [Migration guide](docs/upgrading.md) — switching, behaviour changes and tracing.
+- [Changelog](CHANGELOG.md) · [Roadmap](ROADMAP.md) · [Contributing](CONTRIBUTING.md)
-Also thanks to [Ryan Dahl](https://github.com/ry) for letting me have the `postgres` npm package name.
+Based on [Postgres.js](https://github.com/porsager/postgres) by [Rasmus Porsager](https://github.com/porsager). Thank you to its creator and everyone contributing fixes and reproductions.