Re: [PATCH] OAuth: fix performance bug with stuck multiplexer events

Jacob Champion <jacob.champion@enterprisedb.com>

From: Jacob Champion <jacob.champion@enterprisedb.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Thomas Munro <thomas.munro@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, Peter Eisentraut <peter@eisentraut.org>, Tom Lane <tgl@sss.pgh.pa.us>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, Andrew Dunstan <andrew@dunslane.net>
Date: 2026-04-07T16:05:29Z
Lists: pgsql-hackers
On Tue, Aug 12, 2025 at 3:11 PM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> v5-0002 should fix the more general buildfarm failure that caused the
> revert. The farm finds the new t/ subdirectory and starts running Make
> on src/interfaces/libpq-oauth directly, bypassing the skip logic in
> src/interfaces/Makefile. So I've wrapped the "standard" top-level
> targets that build and install things in a conditional. The targets
> that clean things up have been left alone, at Tom's suggestion in [1].

To avoid surprising anyone: It seems like this suite has remained
stable and fast, so I plan to backpatch it to 18 to keep the coverage
up as the implementations in 19+ diverge.

Thanks,
--Jacob



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. oauth: Always link with -lm for floor()

  2. oauth: Add unit tests for multiplexer handling

  3. oauth: Ensure unused socket registrations are removed

  4. oauth: Remove expired timers from the multiplexer

  5. oauth: Remove stale events from the kqueue multiplexer

  6. oauth: Track total call count during a client flow