TeddyPG Pool

TeddyPG for Bun-native PG pooling.

DatabaseSimple

Stack Components

DBPostgreSQL 16

Poolteddypg 1

RuntimeBun 1

Why

Bun-native, zero-dependency, fast. PostgreSQL is used by nearly 50% of professional developers, making it the most popular database (Stack Overflow 2024).

SQLite powers 1 trillion+ active databases (every iOS/Android device), and DuckDB emerged as the fastest OLAP engine for analytics, 5-10x faster than ClickHouse for single-node queries.

When

Use for Bun PG apps. Avoid for Node (use pg).

How

1. bun add teddypg 2. Create pool 3. Query 4. Close on shutdown 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

const pool = new Pool({ connectionString: process.env.DATABASE_URL }) const rows = await pool.query('SELECT * FROM users')

Common Problems

⚠Bun compat — ensure Bun runtime
⚠Pool size — tune for workload
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use prepared statements
✓Leverage Bun's performance
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is TeddyPG Pool and what projects is it for?

TeddyPG for Bun-native PG pooling. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with TeddyPG Pool in 10 minutes?

Two steps: (1) bun add teddypg; (2) Create pool. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with TeddyPG Pool and how do I avoid it?

The most common pitfall is: Bun compat — ensure Bun runtime. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for TeddyPG Pool?

Best practices for TeddyPG Pool include: Use prepared statements; Leverage Bun's performance; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use prepared statements" — should be set up at project init to avoid costly rework later.

When should I NOT choose TeddyPG Pool?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). TeddyPG Pool shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.