Re: Reviving Time Travel (was Re: 'TID index') - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: Reviving Time Travel (was Re: 'TID index')
Date
Msg-id 20040930215737.GO1297@decibel.org
Whole thread Raw
In response to Re: Reviving Time Travel (was Re: 'TID index')  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: Reviving Time Travel (was Re: 'TID index')
List pgsql-hackers
To answer Simon's earlier comment about if I was looking to start
hacking on PostgreSQL... I'm not. :) I might take a look at the TODO
again, but I seem to do a great job of finding things to put on my plate
as it is. I am interested in minimizing the impact of vacuum, which is
why I brought my idea up originally. So, if anything, I'll be much more
interested to work on improving vacuum than on something else.

Heh, I was about to ask for the pages with dead tuples list to be added
to the TODO, but it seems it's already there ('Maintain a map of
recently-expired rows'). One thing that isn't there which I remember
being discussed was having the page-write daemon do a vacuum of a page
before it's written; has this been done already?
-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Idea about fixing the lockfile issues in postgresql.init
Next
From: Gaetano Mendola
Date:
Subject: Re: Index locking considerations