From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Subject: | Re: Remove lossy-operator RECHECK flag? |
Date: | 2008-04-14 18:28:51 |
Message-ID: | 19670.1208197731@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
>> By the argument that it's better to break things obviously than to
>> break them subtly, risking case 4 seems more attractive than risking
>> case 2.
> The single thought is: usually, it's very hard to see that query returns more
> results that it should be. It doesn't matter for fulltext search (and it has
> very good chance to stay unnoticed forever because wrong rows will be sorted
> down by ranking function, although performance will decrease.
Hmm ... that's a good point. And the performance loss that I'm
complaining about is probably not large, unless you've got a *really*
expensive operator. Maybe we should leave it as-is.
Anybody else have an opinion?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2008-04-14 18:50:36 | Re: Remove lossy-operator RECHECK flag? |
Previous Message | Teodor Sigaev | 2008-04-14 18:23:27 | Re: Remove lossy-operator RECHECK flag? |