| From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
|---|---|
| To: | Andy Colson <andy(at)squeakycode(dot)net> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: texteq/byteaeq: avoid detoast [REVIEW] |
| Date: | 2011-01-17 05:51:59 |
| Message-ID: | AANLkTinURwPsfyaqJRY6P0=fp5ma-ai4NJ2kvF40f+8w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 17, 2011 at 04:05, Andy Colson <andy(at)squeakycode(dot)net> wrote:
> This is a review of:
> https://commitfest.postgresql.org/action/patch_view?id=468
>
> Purpose:
> ========
> Equal and not-equal _may_ be quickly determined if their lengths are
> different. This _may_ be a huge speed up if we don't have to detoast.
We can skip detoast to compare lengths of two text/bytea values
with the patch, but we still need detoast to compare the contents
of the values.
If we always generate same toasted byte sequences from the same raw
values, we don't need to detoast at all to compare the contents.
Is it possible or not?
--
Itagaki Takahiro
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2011-01-17 06:22:40 | Re: texteq/byteaeq: avoid detoast [REVIEW] |
| Previous Message | Oliver Jowett | 2011-01-17 05:00:48 | Re: [HACKERS] Fwd: Weird issues when reading UDT from stored function |