| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Sriram Dandapani <sdandapani(at)counterpane(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: autovacuum |
| Date: | 2006-06-14 20:06:35 |
| Message-ID: | 1150315595.26538.28.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brad Nicholson | 2006-06-14 21:02:25 | Re: Table truncate question |
| Previous Message | Sriram Dandapani | 2006-06-14 16:52:48 | autovacuum |