On Sat, 2007-10-13 at 11:12 +0530, Gokulakannan Somasundaram wrote:
b) But i don't understand how storing the visibility info in TOAST
table would help you. In that case you may need to update it for every
delete/ update happening in the main table. Only thing, it would help
is if someone
Hi Simon/Hannu,
a) I accept with storing ctid in place of oid. That would definitely improve
the performance. I guess it would also remove the restriction of the size on
TOASTABLE ATTRIBUTES. I guess different chunks have to be linked together,
without the index.
b) But i don't understand how
Ühel kenal päeval, E, 2007-10-08 kell 12:12, kirjutas Gokulakannan
Somasundaram:
Hi,
Currently The index implementation in Postgresql does not store
the Snapshot information in the Index.
..
Please reply back with your comments.
I think you got enoght search for previous discussion
On Mon, 2007-10-08 at 14:58 +0300, Hannu Krosing wrote:
1. get rid of indexes for TOAST tables
instead of TOAST tuple id store CTID of first TOAST block directly, and
use something like skip lists inside the TOAST block headers to access
next TOAST tuples.
It should be possible to optimise
