Prev: BUG #4887: inclusion operator (@>) on tsqeriesbehaves not conforming to documentation
Next: query cancel issues in contrib/dblink
From: Gokulakannan Somasundaram on 24 Feb 2010 14:05
Missed the group....



> So basically you want to have index-only scans, but you want them to
> be really slow?
>

No Robert, i just asked him to make it optional, so that the crash safe
visibility map is used only when its need is realized by the DB designer.
When there is a table with no indexes/ a table where the data will be often
updated/ a database where there will be a batch job together with OLTP
stuff, the visibility map is just useless. So i am requesting Heikki to make
it optional. I am not asking him to drop that idea, as it might be useful in
read only environments.

Hope, i have not offended you in conveying that.

Thanks,
Gokul.
 | 
Pages: 1
Prev: BUG #4887: inclusion operator (@>) on tsqeriesbehaves not conforming to documentation
Next: query cancel issues in contrib/dblink