Re: texteq/byteaeq: avoid detoast [REVIEW] - Mailing list pgsql-hackers

From Robert Haas
Subject Re: texteq/byteaeq: avoid detoast [REVIEW]
Date
Msg-id AANLkTikM85u8v+ViscYVGPOiPpH69urs3v=2Y-NW1C_6@mail.gmail.com
Whole thread Raw
In response to Re: texteq/byteaeq: avoid detoast [REVIEW]  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: texteq/byteaeq: avoid detoast [REVIEW]  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Jan 18, 2011 at 11:44 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Tue, Jan 18, 2011 at 11:15 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> No, I don't think so.  Has any evidence been submitted that that part of
>>> the patch is of benefit?
>
>> I think you might be mixing up what's actually in the patch with
>> another idea that was proposed but isn't actually in the patch.  The
>> patch itself does nothing controversial.
>
> Oh, I misread Itagaki-san's comment to imply that that *was* in the
> patch.  Maybe I should go read it.

Perhaps.  :-)

While you're at it you might commit it.  :-)

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: test_fsync open_sync test
Next
From: Robert Haas
Date:
Subject: Re: pg_filedump moved to pgfoundry