4c144f8f7fa0a621900bd30665f243293fd49319
Two claims verified independently before folding: (1) deadpool-postgres discards async notifications — upstream deadpool-rs/deadpool#360 (open, Oct 2024) confirms the pool's connect task awaits the connection to completion, dropping what only poll_message exposes; pooled LISTEN is lost at recycle. The dedicated non-pooled LISTEN connection is now upstream-verified required, not spec-preferred. (2) postgres-notify 0.3.8 exists as described (MIT, tokio-postgres, auto-reconnect with backoff+jitter, multi-channel subscribe_notify, connect_script hook) — admitted as sub-module L's second arm (hand-rolled forwarder vs turnkey listener substrate), with in-probe verification required: docs don't explicitly promise subscription restoration across reconnect; connect_script is the mechanism; single-maintainer posture recorded. New property test pinned: pooled-LISTEN-discard assertion (our own evidence for the #360 behavior, flips if upstream fixes). Probe 5 updated to budget accounting (listener conn outside the pool).
Languages
Rust
99.4%
Python
0.5%