RE: Plans for solving the VACUUM problem

> 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
>