Re: WIP patch: reducing overhead for repeat de-TOASTing

From: Mark Cave-Ayland <mark(dot)cave-ayland(at)siriusit(dot)co(dot)uk>
To: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP patch: reducing overhead for repeat de-TOASTing
Date: 2008-07-01 13:11:28
Message-ID: 486A2D00.5090409@siriusit.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Guillaume Smet wrote:

> From the discussion we had a few months ago, I don't think the no
> RECHECK trick works with CVS tip anymore.
>
> See my post on the "Remove lossy-operator RECHECK flag?" thread:
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg00847.php
> and follow-ups.
>
> That said, perhaps it's not the only problem you have but I thought it
> was worth mentioning.

Yeah sorry, that might not have been as clear as I hoped. What I meant
was that I removed the explicit RECHECK clause from the GiST operator
class definition - since as you correctly mention, CVS tip throws an
error if this is present.

ATB,

Mark.

--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-07-01 13:53:05 Re: WIP patch: reducing overhead for repeat de-TOASTing
Previous Message Zdenek Kotala 2008-07-01 13:10:42 Re: Dept of ugly hacks: eliminating padding space in system indexes