Re: char() overhead on read-only workloads not so insignifcant as the docs claim it is... - Mailing list pgsql-hackers

From Jeremy Kerr
Subject Re: char() overhead on read-only workloads not so insignifcant as the docs claim it is...
Date
Msg-id 200906160843.39560.jk@ozlabs.org
Whole thread Raw
In response to Re: char() overhead on read-only workloads not so insignifcant as the docs claim it is...  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro,

> Maybe bcTruelen could be optimized to step on one word at a time
> (perhaps by using XOR against a precomputed word filled with ' '),
> instead of one byte at a time ...

I have a patch for this, will send soon.

Regards,


Jeremy


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: char() overhead on read-only workloads not so insignifcant as the docs claim it is...
Next
From: Jeremy Kerr
Date:
Subject: [PATCH] backend: compare word-at-a-time in bcTruelen