Re: Suggestion; "WITH VACUUM" option

From: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Suggestion; "WITH VACUUM" option
Date: 2002-12-16 22:15:32
Message-ID: 20021216181433.T15947-100000@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 16 Dec 2002, Josh Berkus wrote:

> Tom, Folks:
>
> Joe and I were discussing your recent discussion about the costs of VACUUM and
> tuple maintainence, and I had an interesting idea.
>
> How hard would it be to add a "WITH (VACUUM)" option to UPDATE and DELETE
> queries? This option would cause the regular vacuum activity -- purging the
> dead tuple and its index references -- to be done immediately, as part of the
> statement, instead of being deferred.
>
> I agree that we don't want immediate tuple maintainence, most of the time.
> However, a couple of my clients would really like to have a few queries do
> their vacuum immediately, and are currently getting around that by vacuuming
> every 5 mintutes.
>
> Easy? Hard? Insane? What do you think?

Just curious, but wouldn't it be just as simple to issue a VACUUM call
right after the UPDATE/DELETE?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2002-12-16 22:25:59 Re: Suggestion; "WITH VACUUM" option
Previous Message Josh Berkus 2002-12-16 22:00:53 Suggestion; "WITH VACUUM" option