Horton

Re: libpq: Process buffered SSL read bytes to support records >8kB on async API

Merlin Moncure <mmoncure@gmail.com>

View thread
From: Merlin Moncure <mmoncure@gmail.com>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Lars Kanis <lars@greiz-reinsdorf.de>, pgsql-hackers@lists.postgresql.org
Date: 2025-07-16T14:36:34Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove incorrect Assert.

On Tue, Jul 15, 2025 at 4:31 PM Jacob Champion <
jacob.champion@enterprisedb.com> wrote

> Otherwise I think we'll continue to chase weird corner cases.
>

Agreed. Here's a little more detail on the case I noticed:

* postgres backend thread managing several libpq connections, with polling
is_busy loop
* when client pushed a lot of log messages (say, with 'RAISE NOTICE'), the
server would stall for significant periods of time, sometimes minutes --
during that time, there would be no activity in the log (the server doesn't
do anything interesting outside of of the polling loop)
* checking backend server log, which relogs the client raised logs via
dblink, each pause happened after roughly 16k bytes
* reducing the log verbosity made the problem go away.

merlin