a vacuum thread is not the answer - Mailing list pgsql-hackers

From mlw
Subject a vacuum thread is not the answer
Date
Msg-id 3C87841F.3E580961@mohawksoft.com
Whole thread Raw
Responses Re: a vacuum thread is not the answer  (Jan Wieck <janwieck@yahoo.com>)
Re: a vacuum thread is not the answer  (Hannu Krosing <hannu@krosing.net>)
List pgsql-hackers
I was just toying around with things, and you know, running vacuum in the
background doesn't work. It slows things down too much.

The worst case senario is when one does this:

update accounts set abalance = abalance + 1 ;

This takes forever to run and doubles the size of the table.

Is there a way that a separate thread managing the freelist can perform a "per
row" vacuum concurrently? Maybe I am stating the problem incorrectly, but we
need to be able to recover rows already in memory for performance.


pgsql-hackers by date:

Previous
From: Fernando Nasser
Date:
Subject: Current cvs source regression: create_function_1.out
Next
From: Jan Wieck
Date:
Subject: Re: Bad Build