Re: Replace some cstring_to_text to cstring_to_text_with_len - Mailing list pgsql-hackers

From Ranier Vilela
Subject Re: Replace some cstring_to_text to cstring_to_text_with_len
Date
Msg-id CAEudQArgvOmO2wRBuJ=3RCfBQUZ=9aaB6-h_Fo+uLfdB6KnTQw@mail.gmail.com
Whole thread Raw
In response to Re: Replace some cstring_to_text to cstring_to_text_with_len  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Replace some cstring_to_text to cstring_to_text_with_len
List pgsql-hackers
Em qui., 31 de ago. de 2023 às 00:22, Michael Paquier <michael@paquier.xyz> escreveu:
On Wed, Aug 30, 2023 at 03:00:13PM -0300, Ranier Vilela wrote:
> cstring_to_text has a small overhead, because call strlen for
> pointer to char parameter.
>
> Is it worth the effort to avoid this, where do we know the size of the
> parameter?

Are there workloads where this matters?
None, but note this change has the same spirit of 8b26769bc.

best regards,
Ranier Vilela

pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: cataloguing NOT NULL constraints
Next
From: John Naylor
Date:
Subject: Re: Should we use MemSet or {0} for struct initialization?