RE: Plans for solving the VACUUM problem - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: Plans for solving the VACUUM problem
Date
Msg-id 3705826352029646A3E91C53F7189E32016635@sectorbase2.sectorbase.com
Whole thread Raw
In response to Plans for solving the VACUUM problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> From: Mikheev, Vadim 
> Sent: Monday, May 21, 2001 10:23 AM
> To: 'Jan Wieck'; Tom Lane
> Cc: The Hermit Hacker; 'Bruce Momjian';
> pgsql-hackers@postgresql.orgrg.us.greatbridge.com

Strange address, Jan?

> Subject: RE: [HACKERS] Plans for solving the VACUUM problem
> 
> 
> >     I think the in-shared-mem FSM could have  some  max-per-table
> >     limit  and  the background VACUUM just skips the entire table
> >     as long as nobody  reused  any  space.  Also  it  might  only
> >     compact pages that lead to 25 or more percent of freespace in
> >     the first place. That makes it more likely  that  if  someone
> >     looks  for  a place to store a tuple that it'll fit into that
> >     block (remember that the toaster tries to  keep  main  tuples
> >     below BLKSZ/4).
> 
> This should be configurable parameter like PCFREE (or something
> like that) in Oracle: consider page for insertion only if it's
> PCFREE % empty.
> 
> Vadim
> 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Is stats update during COPY IN really a good idea?
Next
From: Jan Wieck
Date:
Subject: PL/pgSQL CURSOR support