Re: vacuum row?
- From: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
- To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- Cc: Mark Woodward <pgsql(at)mohawksoft(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: vacuum row?
- Date: Mon, 26 Jun 2006 11:05:59 +0200
- Message-id: <1151312759(dot)3309(dot)227(dot)camel(at)coppola(dot)muc(dot)ecircle(dot)de>
On Sun, 2006-06-25 at 05:29, Alvaro Herrera wrote:
> Mark Woodward wrote:
> > I originally suggested a methodology for preserving MVCC and everyone is
> > confusing it as update "in place," this isnot what I intended.
>
> It doesn't make sense, but maybe vacuuming a page would. Naturally, it
> would need to wholly scan all the indexes to clean'em up, so it's
> probably not a good idea in general.
But a version of vacuum which does normal index scans when vacuuming
just a small percent of a huge table would make sense wouldn't it ? So
you don't need to make full scans of the vacuumed indexes but look up
the entries based on the vacuumed key.
There were discussions about this I think, and the objection was that it
might be that an index scan might miss index entries, in particular when
badly behaved user defined functions are involved.
Cheers,
Csaba.
Home |
Main Index |
Thread Index