Jinwoo Hong eb6068a434 fix(relay): stop a terminated checked-out PostgreSQL client from killing the cell (#21840) ...

pg-pool removes its own `error` listener when it hands a client out
(pg-pool@3.14.0 index.js:344) and only reattaches it in `_release`
(index.js:385). Between acquire and release the client therefore has no
`error` listener, so when Cloud SQL terminates that session mid-statement
the emit becomes an unhandled 'error' event and the process exits.
`absorbPostgresIdleClientErrors` cannot see it: pg-pool routes to
`pool.on('error')` only from the idle listener.

Attach a per-checkout `error` listener in the one seam every relay
checkout passes through, log a single warn line, and release the client
with the error so pg-pool destroys it instead of pooling a dead
connection. The listener is removed on release so it cannot accumulate.
The in-flight query still rejects, so existing failure reporting and the
transaction retry ladder are unchanged.

Claude-Session: https://claude.ai/session/ced32ebb-7155-4413-adad-1eccd14c2010

2026-09-20 17:46:25 -04:00

..

src

fix(relay): stop a terminated checked-out PostgreSQL client from killing the cell (#21840)

2026-09-20 17:46:25 -04:00

Dockerfile

feat(cloud): native push gateway and dedicated infrastructure (1/3) (#19912)

2026-09-10 17:59:46 -04:00

package.json

fix(deps): update vulnerable dependencies without new overrides

2026-09-16 20:36:24 -07:00

tsconfig.build.json

feat(relay): correct regional placement only when the source is idle (#20105)

2026-09-11 14:25:10 -04:00

tsconfig.json

chore(cloud): add the relay fence broker, ops console, Terraform root, scripts, and 24 cloud-* workflows (#18413)

2026-09-03 06:55:14 -04:00

vitest.config.ts

chore(cloud): add the relay fence broker, ops console, Terraform root, scripts, and 24 cloud-* workflows (#18413)

2026-09-03 06:55:14 -04:00