Re: Flushing large data immediately in pqcomm
Jelte Fennema-Nio <postgres@jeltef.nl>
From: Jelte Fennema-Nio <postgres@jeltef.nl>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Melih Mutlu <m.melihmutlu@gmail.com>,
Heikki Linnakangas <hlinnaka@iki.fi>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Thomas Munro <thomas.munro@gmail.com>
Date: 2024-01-31T17:49:40Z
Lists: pgsql-hackers
On Wed, 31 Jan 2024 at 18:23, Robert Haas <robertmhaas@gmail.com> wrote: > That's kind of an odd artifact, but maybe it's fine in > practice. I agree it's an odd artifact, but it's not a regression over the status quo. Achieving that was the intent of my suggestion: A change that improves some cases, but regresses nowhere. > I say again that it's good to test out a bunch of scenarios > and see what shakes out. Testing a bunch of scenarios to find a good one sounds like a good idea, which can probably give us a more optimal heuristic. But it also sounds like a lot of work, and probably results in a lot of discussion. That extra effort might mean that we're not going to commit any change for PG17 (or even at all). If so, then I'd rather have a modest improvement from my refinement of Melih's proposal, than none at all.
Commits
-
Avoid needless large memcpys in libpq socket writing
- c4ab7da60617 17.0 landed