Re: VACUUM ANALYZE -vs- ANALYZE on an insert-only table.

From: "Matt Gordon" <m(dot)gordon(at)f5(dot)com>
To: "Bruno Wolff III" <bruno(at)wolff(dot)to>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: VACUUM ANALYZE -vs- ANALYZE on an insert-only table.
Date: 2003-12-16 20:11:10
Message-ID: 47BC08C8E02BA54EBD901AB9328BFBC09F10E4@exchtwo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

That's what I suspected. Thanks Bruno.

-----Original Message-----
From: Bruno Wolff III [mailto:bruno(at)wolff(dot)to]
Sent: Monday, December 15, 2003 1:38 PM
To: Matt Gordon
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] VACUUM ANALYZE -vs- ANALYZE on an insert-only
table.

On Thu, Dec 11, 2003 at 15:26:56 -0800,
Matt Gordon <m(dot)gordon(at)f5(dot)com> wrote:
> If I have a table that I only use for INSERTs and queries (no UPDATEs or DELETEs), is it enough to just run ANALYZE on the table instead of VACUUM ANALYZE? In other words, is running a VACUUM on a table useful if all that you're doing is INSERTing into it? My understanding of VACUUM is that it cleans up stale tuples that are left after UPDATEs and DELETEs.
>

You only need to vacuum if you do updates, deletes or when you need to
handle wrap around of transaction IDs (about every 10^9 transactions).

Browse pgsql-general by date

  From Date Subject
Next Message Matt Gordon 2003-12-16 20:26:43 Re: VACUUM ANALYZE -vs- ANALYZE on an insert-only table.
Previous Message Paul Ganainm 2003-12-16 19:21:03 Re: add column sillyness