On 6/23/06, Mark Woodward <[EMAIL PROTECTED]> wrote:
Rather than keep references to all versions of all rows in indexes, keep only a reference to the first or "key" row of each row, and have the first version of a row form the head of a linked list to subsequent versions of each row. The list will be in decending order.
By all means, please go ahead and try it because it's not quite that easy. You're going to run into serious locking and contention issues this way. In the end, it's not much better than running a sequential scan to query a row that's been updated several thousand times on a table that hasn't been vacuumed... follow that pointer :) -- Jonah H. Harris, Software Architect | phone: 732.331.1300 EnterpriseDB Corporation | fax: 732.331.1301 33 Wood Ave S, 2nd Floor | [EMAIL PROTECTED] Iselin, New Jersey 08830 | http://www.enterprisedb.com/ ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
