Tom Lane [EMAIL PROTECTED] writes:
Greg Stark [EMAIL PROTECTED] writes:
But on that note, is it ok to use the bulkdelete index AM methods for
non-vacuum purposes
Um, what would those be?
I'm sure with a little work I can imagine lots of reasons to want to pull out
all the index tuples
On Wed, Jul 05, 2006 at 09:14:21PM -0400, Greg Stark wrote:
Well what was tripping me up was figuring out the operator class. I just
realized it's in the index's Relation object.
But yes what you describe is really a problem. Even given the operator class
there's no way for me to know which
Greg Stark [EMAIL PROTECTED] writes:
I'm a bit confused about how scan keys work. Is there any simple way given a
list of Datums of the same type as the index tuple attributes to get all
matching index entries? This is for a non-system index.
Define matching.
I tried just using
Tom Lane [EMAIL PROTECTED] writes:
I tried just using index_getprocinfo(...,BTORDER) with InvalidStrategy like
btree does but _bt_preprocess_keys runs into problems without a valid
strategy
number. And in any case that would be btree specific which seems like it
ought
not be
Greg Stark [EMAIL PROTECTED] writes:
But on that note, is it ok to use the bulkdelete index AM methods for
non-vacuum purposes
Um, what would those be?
ambulkdelete and amvacuumcleanup are most certainly not designed to be
used in any context other than VACUUM. You might be able to abuse them
I'm a bit confused about how scan keys work. Is there any simple way given a
list of Datums of the same type as the index tuple attributes to get all
matching index entries? This is for a non-system index.
It seems like the only place in the code where non-system index lookups are
done is
On Wed, Jul 05, 2006 at 12:00:05PM -0400, Greg Stark wrote:
I'm a bit confused about how scan keys work. Is there any simple way given a
list of Datums of the same type as the index tuple attributes to get all
matching index entries? This is for a non-system index.
A scankey determines which
Martijn van Oosterhout kleptog@svana.org writes:
The info you need is in the operator class. In a sense you do need to
know the type of index you're scanning, not all indexes use the same
strategy numbers.
Well what was tripping me up was figuring out the operator class. I just
realized it's
