Re: Why vacuum? - Mailing list pgsql-hackers

From Daniele Orlandi
Subject Re: Why vacuum?
Date
Msg-id 3A39024A.DF9E3AD8@orlandi.com
Whole thread Raw
In response to AW: Why vacuum?  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
"Ross J. Reedstrom" wrote:
> 
> On Thu, Dec 14, 2000 at 12:07:00PM +0100, Zeugswetter Andreas SB wrote:
> >
> > The tendency here seems to be towards an improved smgr.
> > But, it is currently extremely cheap to calculate where a new row
> > needs to be located physically. This task is *a lot* more expensive
> > in an overwrite smgr.

I don't agree. If (as I have proposed) the search is made in the
background by a low priority process, you just have to lookup a cache
entry to find out where to write.

> > It needs to maintain a list of pages with free slots,
> > which has all sorts of concurrency and persistence problems.

Concurrency is a problem, but a spinlock on a shared-memory table should
suffice in the majority of the cases[1]. I may be wrong... but I think
it should be discussed.

[1] I believe that already there's a similar problem to synchronize the
backends when the want to append a new page.

Bye!


pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SB
Date:
Subject: switching txlog file in 7.1beta
Next
From: Alfred Perlstein
Date:
Subject: Re: Why vacuum?