IT and Web GIS Solutions

  🚨 Why Dynamic PostgreSQL Connection Pools Work Locally but Fail in Production If you’ve ever built a Node.js API using PostgreSQL and pg.Pool , you might have faced this confusing situation: “My code works perfectly on my local machine, but br eaks on the server.” This issue commonly appears when using dynamic PostgreSQL databases together with connection pooling. It often stays hidden during development and surfaces only after deployment. This article explains why this happens , how to identify the root cause , and what a production‑safe architecture looks like . 🧩 The Problematic Pattern A common implementation looks like this: const pools = {}; // cache pools per theme function getThemePool(theme) { if (!pools[theme]) { pools[theme] = new pg.Pool({ user: process.env.DB_USER, host: process.env.DB_HOST, database: theme, // dynamic database password: process.env.DB_PASSWORD, port: process.env.DB_PORT, max: 10 }); } return pool...