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

From: Jeremy Kerr <jk(at)ozlabs(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Subject: Re: char() overhead on read-only workloads not so insignifcant as the docs claim it is...
Date: 2009-06-16 00:43:39
Message-ID: 200906160843.39560.jk@ozlabs.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

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