Heroku与PSQL报错：Cannot read property 'query' of null 求助

Hey there! I totally get the frustration when switching from pg.connect to the pool and hitting this null client error—let's break down how to fix this step by step.

The Root Issue #

Your error happens because the client variable is null when you try to call client.query(). This usually means either your pool wasn't initialized correctly, or you didn't properly acquire a client from the pool before attempting to use it.

Step 1: Correctly Initialize the Pool #

First, make sure you're setting up the pool with the right configuration for Heroku. Heroku's Postgres requires SSL connections, so don't skip that critical setting:

const { Pool } = require('pg');

// Initialize the pool with Heroku's DATABASE_URL and required SSL settings
const pool = new Pool({
  connectionString: process.env.DATABASE_URL,
  ssl: {
    rejectUnauthorized: false // Mandatory for Heroku Postgres connections
  }
});

Note: For local testing, use a .env file with dotenv to load your local database URL instead of relying on Heroku's environment variable.

Step 2: Use the Pool Properly #

You have two reliable ways to run queries without hitting the null client issue:

Option 1: Use pool.query() (Simplest Approach)

The pool has a built-in query method that handles acquiring and releasing connections automatically—no need to manage clients manually:

// Run the query directly through the pool
pool.query('SELECT * FROM test_table', (err, result) => {
  if (err) {
    console.error('Query failed:', err);
    return;
  }
  console.log('Query results:', result.rows);
});

Option 2: Manually Acquire & Release a Client

If you need to run multiple queries in a single transaction, use pool.connect() to get a client—but always remember to release it back to the pool:

pool.connect((err, client, release) => {
  // First, check if there was an error getting the client
  if (err) {
    return console.error('Failed to acquire client from pool:', err.stack);
  }

  // Execute your query
  client.query('SELECT * FROM test_table', (err, result) => {
    // Release the client back to the pool BEFORE handling errors
    release();

    if (err) {
      return console.error('Query execution failed:', err.stack);
    }

    console.log('Query results:', result.rows);
  });
});

Critical: Forgetting release() will drain your connection pool over time, leading to more errors down the line.

Step 3: Verify Your Environment Variables #

Make sure DATABASE_URL is correctly set in your Heroku app. You can check this by running:

heroku config:get DATABASE_URL

If it's missing, reattach your Heroku Postgres addon or set it manually via the Heroku dashboard.

Why Your Original Code Failed #

Chances are you either didn't initialize the pool correctly (missing SSL or using an invalid connection string), or you tried to use a client without properly acquiring it from the pool—resulting in client being null when you called query().

By following the steps above, you should be able to resolve the null client error and get your queries running smoothly on Heroku.

内容的提问来源于stack exchange，提问作者user1590336