From: Joshua D. Drake <jd@commandprompt.com>
To: Mike Goldner <mgoldner@agmednet.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum Problems (locking)
Date: Wed, 25 Oct 2006 12:58:07 -0700
Message-ID: <453FC1CF.4030208@commandprompt.com> (raw)
In-Reply-To: <1161806057.2095.154.camel@localhost.localdomain>
References: <1161806057.2095.154.camel@localhost.localdomain>
Mike Goldner wrote:
> I have a nightly vacuum scheduled as follows:
>
> su - postgres -c "/usr/bin/vacuumdb --analyze --dbname=mydb"
>
> Last night, it appears that the vacuum blocked db access from my
> application server (JBoss). Here is the logfile snippet:
>
> [3693-jbossdb-postgres-2006-10-25 06:52:29.488 EDT]NOTICE: number of
> page slots needed (559472) exceeds max_fsm_pages (200000)
> [3693-jbossdb-postgres-2006-10-25 06:52:29.488 EDT]HINT: Consider
> increasing the configuration parameter "max_fsm_pages" to a value over
> 559472.
> [3693-jbossdb-postgres-2006-10-25 06:52:29.488 EDT]LOG: number of page
> slots needed (559472) exceeds max_fsm_pages (200000)
> [3693-jbossdb-postgres-2006-10-25 06:52:29.488 EDT]HINT: Consider
> increasing the configuration parameter "max_fsm_pages" to a value over
> 559472.
> [3693-jbossdb-postgres-2006-10-25 06:52:29.530 EDT]LOG: transaction ID
> wrap limit is 1073813592, limited by database "benchpg"
> [3693-jbossdb-postgres-2006-10-25 06:52:29.530 EDT]LOG: transaction ID
> wrap limit is 1073813592, limited by database "benchpg"
> [3693-jbossdb-postgres-2006-10-25 06:52:29.530 EDT]LOG: duration:
> 10224738.050 ms statement: VACUUM ANALYZE;
>
> First of all, my max_fsm_pages is obviously way off. However, every
> time I increase my max_fsm_pages the next vacuum says that it requires
> more. Will there every be a plateau in the requested pages? What is
> the impact of exceeding the pages slots needed?
You will need to vacuum full and if your need continues to grow, you
need to vacuum more.
> The only semi-unusual characteristic of my database is that I have one
> table in particular that grows and shrinks dramatically. My entire
> database after a vacuum --full is about 8GB. However, after a day or
> two, the db will grow as large as 75GB. Truncating that one table
> (since it empties regularly) will shrink the db right back to the 8GB.
Vacuum that single table, ALOT.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: jd@commandprompt.com, mgoldner@agmednet.com
Subject: Re: Vacuum Problems (locking)
In-Reply-To: <453FC1CF.4030208@commandprompt.com>
References: <1161806057.2095.154.camel@localhost.localdomain> <453FC1CF.4030208@commandprompt.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