[HACKERS] Can get GiST RECHECK clause to work

2004-06-13 Thread Mark Cave-Ayland
Hi everyone, I'm trying to mark a GiST index as lossy using the RECHECK operator as part of some work on PostGIS, but what happens is that the original operator function is never reapplied to the results of the index scan. The operator class and operator definitions looks like this: CREATE

Re: [HACKERS] Can get GiST RECHECK clause to work

2004-06-13 Thread Tom Lane
Mark Cave-Ayland [EMAIL PROTECTED] writes: I'm trying to mark a GiST index as lossy using the RECHECK operator as part of some work on PostGIS, but what happens is that the original operator function is never reapplied to the results of the index scan. You sure? I'm pretty sure that a number

Re: [HACKERS] Can get GiST RECHECK clause to work

2004-06-13 Thread Mark Cave-Ayland
To: Mark Cave-Ayland Cc: [EMAIL PROTECTED] Subject: Re: [HACKERS] Can get GiST RECHECK clause to work Mark Cave-Ayland [EMAIL PROTECTED] writes: I'm trying to mark a GiST index as lossy using the RECHECK operator as part of some work on PostGIS, but what happens is that the original

Re: [HACKERS] Can get GiST RECHECK clause to work

2004-06-13 Thread Tom Lane
Mark Cave-Ayland [EMAIL PROTECTED] writes: As far as I can tell this is the case. What I've done to test this is to put an elog(NOTICE, .) in geometry_overlap() Well, I can easily prove that CVS tip does call the operator function and honor its result. regression=# create table foo (f1