On Thu, Sep 24, 2026 at 8:50 AM Merlin Moncure <mmoncure@gmail.com> wrote:
My work on adding a WaitEventSet based dblink API poll was in part inspired by attempting to defend against this issue on the premise that sitting around in poll() and being aggressive with consumeinput vs pg_sleep latch was somehow more polite to the o/s somehow. Perhaps it's not a bug at all, but a simple hardware flush problem that postgres is at the mercy of.
Quick note: turning off logging collector, then disconnecting the session that invoked pg_ctl so that logs go nowhere, timings go flat and are fast. So this smells like hardware.
