Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> * Make CLUSTER error out if the target index is not of an 'amindexnulls'
>> index AM. This would amount to restricting CLUSTER to b-trees, which is
>> annoying.
> I think this solution is fine - we just need to fix GiST to index nulls
> one d
Rod Taylor <[EMAIL PROTECTED]> writes:
> I'm willing to do this:
I can handle it (was already working on it, in fact). I had hoped to
find someone who might want to do the more extensive fix, but erroring
out is easy enough.
> - Reject on partial or functional indexes
> - Reject when first colum
> * Make CLUSTER error out if the target index is not of an 'amindexnulls'
> index AM. This would amount to restricting CLUSTER to b-trees, which is
> annoying.
I'm willing to do this:
- Reject on partial or functional indexes
- Reject when first columns attnotnull is false and amindexnulls is
[ repost, as original message of 28-Feb seems to have gotten lost ]
I said:
> I was able to reproduce a problem as follows: run the tsearch regression
> test, then do "cluster wowidx on test_txtidx". This appears to lose
> one row:
Ahh ... it took me way too long to realize what was happening.