From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Sriram Dandapani <sdandapani@counterpane.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum
Date: Wed, 14 Jun 2006 15:06:35 -0500
Message-ID: <1150315595.26538.28.camel@state.g2switchworks.com> (raw)
In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF04C4C928@ca-mail1.cis.local>
References: <6992E470F12A444BB787B5C937B9D4DF04C4C928@ca-mail1.cis.local>
On Wed, 2006-06-14 at 11:52, Sriram Dandapani wrote:
> Hi
>
>
>
> I have a table into which data flows at a high rate say 2 million rows
> per hour. Every 15 minutes, these rows are processed and deleted.
>
> At any point in time, the row count for the table hovers around 500K
> (due to the deletes).
>
>
>
> I have set max_fsm_pages to about 2000000. I still see the
> pg_total_relation_size constantly reporting an increasing size.
>
>
>
> How do I know if autovacuum is reclaiming space or is my max_fsm
> setting plain wrong. (I understand that autovacuum marks tuples for
> reuse, but shouldn’t pg_total_relation_size take that into account)
I wouldn't really rely on just autovacuum to do this.
But, if you must, adjust the threshholds to have it trigger more easily.
Me personally, if I'm running a script that deletes 500,000 rows, I put
a vacuum at the end of it. That way you KNOW the vacuum got run.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: smarlowe@g2switchworks.com, sdandapani@counterpane.com
Subject: Re: autovacuum
In-Reply-To: <1150315595.26538.28.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox