Re: Name for new VACUUM

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Name for new VACUUM
Date: 2001-08-05 17:38:31
Message-ID: 3B6D8497.55E3094A@tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
>
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > >> Not necessarily. Concurrent VACUUM does truncate the relation if it can
> > >> do so conveniently --- for example, it will successfully reclaim space
> > >> if you do "DELETE FROM foo; VACUUM foo;". It just doesn't try as hard
> > >> as the older VACUUM code does.
> >
> > > But it will not reclaim from UPDATE.
> >
> > What? I have no idea what you mean by that.
>
> I meant that UPDATE of all rows in a table put the new rows at the end.

OTOH if you do it twice it will reclaim ;)

UPDATE everything;
VACUUM;
UPDATE everything;
VACUUM;

---------------
Hannu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2001-08-05 17:45:47 Re: Re: Name for new VACUUM
Previous Message mlw 2001-08-05 14:59:48 Re: Re: OID wraparound: summary and proposal