Date: Wed, 19 Mar 2008 09:55:59 -0400
From: Bill Moran <wmoran@collaborativefusion.com>
To: "Mark Steben" <msteben@autorevenue.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: question on TRUNCATE vs VACUUM FULL
Message-Id: <20080319095559.9de777dd.wmoran@collaborativefusion.com>
In-Reply-To: <011f01c889c7$2b421f30$14010a0a@dei26g028575>
References: <20080319093450.29f6cf6e.wmoran@collaborativefusion.com>
	<011f01c889c7$2b421f30$14010a0a@dei26g028575>
Organization: Collaborative Fusion
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

In response to "Mark Steben" <msteben@autorevenue.com>:

> Bill,
> Thanks for your quick response.
> We are at version 8.2.5 - just recently upgraded from 7.4.5.
> This strategy using truncate was just implemented yesterday.
> Now I will revisit the vacuum full strategy. Does seem to
> Be redundant.
> Is there a procedure to begin reporting a bug?  Is there
> Someone or an email address that I could bring evidence to?

You're kinda on the right path already.  The next thing to do (if nobody
gets back to you with an explanation or solution) is to put together a
simple, reproducible case that others can use to reproduce the behaviour
on systems where they can investigate it.  Once you have that, use the
bug reporting form on the web site to report it as a bug.

-- 
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran@collaborativefusion.com
Phone: 412-422-3463x4023