In article <[EMAIL PROTECTED]>,
Adam Siegel <[EMAIL PROTECTED]> wrote:
[...]
% We perform a vacuum full after each mass delete. This cycle can happen
% many times during over a couple of weeks. We are in a test lab
% environment and are generating a lot of data.
%
% One of the problems we ha
Isn't this also a symptom of inappropriate FSM settings?
Try running a VACUUM VERBOSE and check the FSM settings at the end.
-tfo
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source — Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashv
On Wed, Mar 30, 2005 at 13:09:33 -0500,
Adam Siegel <[EMAIL PROTECTED]> wrote:
>
> We perform a vacuum full after each mass delete. This cycle can happen
> many times during over a couple of weeks. We are in a test lab
> environment and are generating a lot of data.
>
> One of the problems
Adam Siegel wrote:
> We have a system that archives data to a postgres database. The raw
> data is confined to one table. Each record in the table is generally
> 1500 bytes. Each record is also associated with a volume name.
> During normal operations, many millions of rows are written to this
On 3/30/05 12:09 PM, "Adam Siegel" <[EMAIL PROTECTED]> wrote:
> How can we physically recover "real" disk space for the rows that were
> deleted from the table?
vacuum full
Wes
---(end of broadcast)---
TIP 8: explain analyze is your friend
We have a system that archives data to a postgres database. The raw
data is confined to one table. Each record in the table is generally
1500 bytes. Each record is also associated with a volume name. During
normal operations, many millions of rows are written to this table.
After sometime
