From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | Patches <pgsql-patches(at)postgresql(dot)org>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
Subject: | Re: Bitmapscan changes |
Date: | 2007-03-12 16:51:48 |
Message-ID: | 16883.1173718308@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> Tom Lane wrote:
>> This will not work, unless we change the planner --- the original quals
>> aren't necessarily there in some corner cases (partial indexes, if
>> memory serves).
> This is only for bitmap scans, which *do* always have the original quals
> available in the executor (BitmapHeapScanState.bitmapqualorig).
> That's because we have to recheck the original conditions when the
> bitmap goes lossy.
Yeah, but the index AM has to support regular indexscans too, and those
are not prepared for runtime lossiness determination; nor am I
particularly willing to add that.
> With the unapplied GIT patch, the index doesn't store the index key of
> every tuple.
I thought the design was to eliminate *duplicate* keys from the index.
Not to lose data.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-03-12 17:02:10 | Re: Bitmapscan changes |
Previous Message | Heikki Linnakangas | 2007-03-12 16:34:07 | Re: Bitmapscan changes |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-03-12 17:02:10 | Re: Bitmapscan changes |
Previous Message | Heikki Linnakangas | 2007-03-12 16:34:07 | Re: Bitmapscan changes |