Skip to content
← Back to activity

Immutable solution version

pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection

Version 1Sign in to save

Complete solution

How to fix 'pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection' in Neon, straight from the verified resolution in gh:neondatabase/serverless#209. Root cause plus what to change.

What was reported

Issue neondatabase/serverless#209 (closed, 5 comments): ## Bug: pipelineConnect silently hangs for payloads in ~32KB - 42KB range on pool reconnection

Description

When pipelineConnect is set to "password" (the default for Neon hosts), queries that are the first on a newly created connection (after pool idle reaping) silently hang - the Promise never resolves and no error is thrown - if the total wire message falls within a specific size range (~32KB - 42KB of JSON parameter data).

Payloads below and above this range work correctly on reconnection. The issue only manifests when all three conditions are true simultaneously:

  1. **Connect

The verified resolution

[jawj (maintainer)]: Bug is in Neon's proxy code, not the npm package: with pipelineConnect, a first query of roughly 65-84KB wire size (Prisma sends UPSERT data twice - once for INSERT, once for UPDATE branch) silently hung. Fixed server-side on production; no package update needed. Reporter confirmed the hang no longer occurs.

Evidence

Asked in gh:neondatabase/serverless#209 (https://github.com/neondatabase/serverless/issues/209): pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection. The issue report: Issue neondatabase/serverless#209 (closed, 5 comments): ## Bug: pipelineConnect silently hangs for payloads in ~32KB - 42KB range on pool reconnection

Description

When pipelineConnect is set to "password" (the default for Neon hosts), queries that are the first on a newly created connection (after pool idle reaping) silently hang - the Promise never resolves and no error is thrown - if the total wire message falls within a specific size range (~32KB - 42KB of JSON parameter data).

Payloads below and above this range work correctly on reconnection. The issue only manifests when all three conditions are true simultaneously:

  1. **Connect The verified answer: [jawj (maintainer)]: Bug is in Neon's proxy code, not the npm package: with pipelineConnect, a first query of roughly 65-84KB wire size (Prisma sends UPSERT data twice - once for INSERT, once for UPDATE branch) silently hung. Fixed server-side on production; no package update needed. Reporter confirmed the hang no longer occurs.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_48h_sz9IlIKHNbeeTDym2w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection <span>— Vectle</span></a>