From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
---|---|
To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Add pg_strtoupper and pg_strtolower functions |
Date: | 2022-05-02 13:13:20 |
Message-ID: | CAExHW5tiU62_i+=CWgLBc7Wzdhh5dU6YAt78YUTPsh-5hZKV2w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 2, 2022 at 6:21 PM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> Hi,
>
> I came across pg_toupper and pg_tolower functions, converting a single
> character, are being used in loops to convert an entire
> null-terminated string. The cost of calling these character-based
> conversion functions (even though small) can be avoided if we have two
> new functions pg_strtoupper and pg_strtolower.
Have we measured the saving in cost? Let's say for a million character
long string?
>
> Attaching a patch with these new two functions and their usage in most
> of the possible places in the code.
Converting pg_toupper and pg_tolower to "inline" might save cost
similarly and also avoid code duplication?
--
Best Wishes,
Ashutosh Bapat
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2022-05-02 13:14:19 | Re: Unfiltered server logs routing via a new elog hook or existing emit_log_hook bypassing log_min_message check |
Previous Message | Bharath Rupireddy | 2022-05-02 13:10:05 | Re: Unfiltered server logs routing via a new elog hook or existing emit_log_hook bypassing log_min_message check |