Next.js+PostgreSQL

Next.js and PostgreSQL are a staple of the 'T3' and modern full-stack ecosystem. When running in the standard Node.js runtime, the pg driver or ORMs like Prisma and Drizzle work flawlessly. This setup allows for persistent connection pooling and full access to PostgreSQL's features via the standard TCP protocol.

The 'Partial' status arises when developers attempt to use PostgreSQL within Next.js Edge Runtime (e.g., middleware or Edge API routes). Because Edge environments lack access to Node's internal net and tls modules, standard drivers will throw a 'module not found' error during the build or runtime. To solve this, you must either force the route to use the Node.js runtime via export const runtime = 'nodejs' or switch to a driver that supports WebSockets or HTTP tunneling, such as Neon's serverless driver.

Furthermore, connection management is a concern in serverless environments. Standard PostgreSQL connections are heavy; using a connection pooler like PgBouncer or a managed service that handles pooling is highly recommended to prevent 'too many clients' errors during traffic spikes.