Re: Optimization for lower(), upper(), casefold() functions. - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Optimization for lower(), upper(), casefold() functions.
Date
Msg-id deca9cd8a3a84be794706ca8f38646ac6d757f0d.camel@j-davis.com
Whole thread Raw
In response to Re: Optimization for lower(), upper(), casefold() functions.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Optimization for lower(), upper(), casefold() functions.
List pgsql-hackers
On Tue, 2025-03-18 at 11:11 -0400, Tom Lane wrote:
> It's not apparent to me why that table needs to be in a header
> file and not in the sole user .c file?

Thank you, fixed.

> Also, probably better to make it const:
>
> -static const pg_wchar *casekind_map[NCaseKind] =
> +static const pg_wchar * const casekind_map[NCaseKind] =

Fixed also (except pgindent had a slightly different opinion about
spaces).

Was this a general suggestion, or did you see something in particular
that would make it more optimizable this way?

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Using read_stream in index vacuum
Next
From: Álvaro Herrera
Date:
Subject: Re: optimize file transfer in pg_upgrade