Re: Visibility map thoughts

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Cc: "Jeff Davis" <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Visibility map thoughts
Date: 2007-11-06 13:19:16
Message-ID: e51f66da0711060519q2158b3a1pbf6120b283b7b4bb@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/6/07, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> wrote:
> Jeff Davis wrote:
> > On Mon, 2007-11-05 at 09:52 +0000, Heikki Linnakangas wrote:
> >> It's not useful for VACUUM FREEZE, unless we're willing to freeze much
> >> more aggressively, and change the meaning of a set bit to "all tuples on
> >> heap page are frozen".
> >
> > This means that a regular VACUUM will no longer be enough to ensure
> > safety from transaction id wraparound.
>
> Good point. So we'd still need regular VACUUMs every now and then.
>
> (Gosh, we really need a name for the sort of vacuum. I was about to say
> "we'd still need regular regular VACUUMs" :-))

As the new VACUUM variant will be somewhat unsafe, it should
not replace "regular" VACUUM but get separate name.

VACUUM FAST maybe? Informally "fastvacuum". Something with
"lazy" or "partial" would also be possibility.

--
marko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2007-11-06 13:22:09 Fix pg_dump dependency on postgres.h
Previous Message Marko Kreen 2007-11-06 13:17:05 Re: Visibility map thoughts