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

From Hiroshi Inoue
Subject Re: Plans for solving the VACUUM problem
Date
Msg-id 3B04C948.4A98D77C@tpf.co.jp
Whole thread Raw
In response to Plans for solving the VACUUM problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> 
> Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > Tom Lane wrote:
> 
> > And would the truncation occur that often in reality under
> > the scheme(without tuple movement) ?
> 
> Probably not, per my comments to someone else.  I'm not very concerned
> about that, as long as we are able to recycle freed space within the
> relation.
> 

Agreed.

> We could in fact move tuples if we wanted to --- it's not fundamentally
> different from an UPDATE --- but then VACUUM becomes a transaction and
> we have the WAL-log-traffic problem back again.

And it has been always the cause of bugs and innefficiency
of VACUUM IMHO.

regards,
Hiroshi Inoue


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Plans for solving the VACUUM problem
Next
From: Tom Lane
Date:
Subject: Re: AW: Adding index flag showing tuple status