Re: Flushing large data immediately in pqcomm

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Flushing large data immediately in pqcomm
Date: 2024-04-09 12:02:55
Message-ID: CAEudQAp2X-Q-U_SfOrSVsOgnUx=CRFzPMu_LhFAsQOtjL0R1UA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em seg., 8 de abr. de 2024 às 09:27, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
escreveu:

> On Sun, 7 Apr 2024 at 11:34, David Rowley <dgrowleyml(at)gmail(dot)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).
>
+1.
Looks ok to me.
The GSS pointer *ptr, is already cast to char * where it is needed,
so the code is already correct.

best regards,
Ranier Vilela

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2024-04-09 12:27:31 Re: PostgreSQL 17 Release Management Team & Feature Freeze
Previous Message Andrew Dunstan 2024-04-09 11:54:25 Re: WIP Incremental JSON Parser