pg-pool
npmv3.14.0Connection pool for node-postgres
Safe to adopt
Yes — pg-pool scores well across adoption, maintenance, weight, supply chain, and licensing. 43.5M downloads per week and 1 known dependents. Last published 114 days ago. 16 releases in the last 2 years.
- AAdoption: grade A, Excellent.
43.5M downloads per week and 1 known dependents.
- BMaintenance: grade B, Good.
Last published 114 days ago. 16 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 29 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding pg-pool to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- ESM + CommonJS
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the pg-pool README.
const Pool = require('pg-pool')
// by default the pool uses the same
// configuration as whatever `pg` version you have installed
const pool = new Pool()
// you can pass properties to the pool
// these properties are passed unchanged to both the node-postgres Client constructor
// and the pool constructor, allowing you to fully configure the behavior of both
const pool2 = new Pool({
database: 'postgres',
user: 'brianc',
password: 'secret!',
port: 5432,pg-pool vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| pg-poolthis page | 43.5M | 1 | MIT | 3 months ago |
| pg | 46.3M | 5 | MIT | 1 day ago |
| drizzle-orm | 19M | 0 | Apache-2.0 | 1 day ago |
| postgres | 0 | 1 | Unlicense | 1 day ago |
| pgpass | 33M | 1 | MIT | 1 day ago |
| knex | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by pg-pool v3.14.0. Runtime dependencies are installed with the package; dev dependencies are not.
Peer (1)
Dev (5)
Used by
Popular packages that depend on pg-pool.
Relationship graph
Dependencies (left) and dependents (right) of pg-pool.
Frequently installed together
A socket implementation that can run on Cloudflare Workers using native TCP connections.
Next generation testing framework powered by Vite
The postgres client/server binary protocol, implemented in TypeScript
Functions for dealing with a PostgreSQL connection string
Module for reading .pgpass
generator async control flow goodness
A slightly nicer interface to Postgres over node-libpq
TypeScript typings for Cloudflare Workers
Release history
15 releases in the last two years, typically about 37 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 3.14.0latest | 3 months ago | 29 KB | MIT |
| 3.13.0 | 6 months ago | 29 KB | MIT |
| 3.12.0 | 6 months ago | 28 KB | MIT |
| 3.11.0 | 7 months ago | 28 KB | MIT |
| 3.10.1 | 1 year ago | 29 KB | MIT |
| 3.10.0 | 1 year ago | 29 KB | MIT |
| 3.9.6 | 1 year ago | 29 KB | MIT |
| 3.9.5 | 1 year ago | 29 KB | MIT |
| 3.9.2 | 1 year ago | 29 KB | MIT |
| 3.9.1 | 1 year ago | 29 KB | MIT |
| 3.9.0 | 1 year ago | 29 KB | MIT |
| 3.8.1-alpha.1 | 1 year ago | 29 KB | MIT |
| 3.8.1-alpha.0 | 1 year ago | 29 KB | MIT |
| 3.8.0 | 1 year ago | 68 KB | MIT |
| 3.7.1 | 1 year ago | 68 KB | MIT |
Overview
pg-pool is an npm package that connection pool for node-postgres. It is extremely widely used, with about 43.5M downloads per week and 1 known dependents in the graph. The latest version is 3.14.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need connection pool for node-postgres and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (43.5M weekly downloads).
- Clear open-source license (MIT).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use pg-pool?
Yes — pg-pool scores well across adoption, maintenance, weight, supply chain, and licensing. 43.5M downloads per week and 1 known dependents. Last published 114 days ago. 16 releases in the last 2 years.
How do I install pg-pool?
Run `npm install pg-pool` to add pg-pool to your npm project.
What license is pg-pool released under?
pg-pool is distributed under the MIT license.
How popular is pg-pool?
pg-pool has approximately 43,483,281 downloads per week and 1 known dependent packages.
Is pg-pool still maintained?
The most recent release of pg-pool (v3.14.0) was published 3 months ago.
Does pg-pool run install scripts?
No. pg-pool does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.