Re: Flushing large data immediately in pqcomm - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: Flushing large data immediately in pqcomm
Date
Msg-id CAGECzQRQ-i7kEiA7jtjC_VjDUOhykcJUMsy6bj8kwe5+k+9-yw@mail.gmail.com
Whole thread Raw
In response to Re: Flushing large data immediately in pqcomm  (Jelte Fennema-Nio <postgres@jeltef.nl>)
Responses Re: Flushing large data immediately in pqcomm
List pgsql-hackers
On Sun, 7 Apr 2024 at 11:34, David Rowley <dgrowleyml@gmail.com> wrote:
> That seems to require modifying the following function signatures:
> secure_write(), be_tls_write(), be_gssapi_write().  That's not an area
> I'm familiar with, however.

Attached is a new patchset where 0003 does exactly that. The only
place where we need to cast to non-const is for GSS, but that seems
fine (commit message has more details).

I also added patch 0002, which is a small addition to the function
comment of internal_flush_buffer that seemed useful to me to
differentiate it from internal_flush (feel free to ignore/rewrite).

Attachment

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum
Next
From: Masahiko Sawada
Date:
Subject: Re: Improve eviction algorithm in ReorderBuffer