(Prompted by nearby thread about VACUUM FULL bugs, but not having
anything to do with that properly speaking.)
Hackers,
For some time, I have wondered: what does postgres use "t_ctid chains"
for? It seems like it is useful to find the "newer" version of a
tuple. However, wouldn't that eventually get found anyway? A
sequential scan scans the whole table, and so it will find the new
tuple. Since indexes contain all tuples, so will an index scan.
I infer that the there must be some sort of optimization to make it
worth (a) using extra space in the disk pages and (b) causing the extra
complexity such as the bugs mentioned in VACUUM FULL.
So: what are the t_ctid chains good for? If this is too long or too
elementary to type, can someone point me to the source code that uses
t_ctid chains?
Regards,
Paul Tillotson
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
