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

From Jan Wieck
Subject Re: a vacuum thread is not the answer
Date
Msg-id 200203072116.g27LGGw25082@saturn.janwieck.net
Whole thread Raw
In response to a vacuum thread is not the answer  (mlw <markw@mohawksoft.com>)
List pgsql-hackers
mlw wrote:
> 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.
   So  you want to reuse space from rows before your transaction   committed? Fine, I'm all for it, as long as
       begin ;       update accounts set abalance = abalance + 1 ;       rollback ;
   still works.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



pgsql-hackers by date:

Previous
From: "Jim Buttafuoco"
Date:
Subject: Re: Storage Location / Tablespaces (try 3)
Next
From: Neil Conway
Date:
Subject: pg_class -> reltuples?