From: | Greg Spiegelberg <gspiegelberg(at)cranel(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Vacuum & Memory Exhausted error |
Date: | 2003-06-17 14:33:48 |
Message-ID: | 3EEF26CC.9020102@cranel.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Morning,
I have multiple databases running on a Solaris 9, PostgreSQL 7.3.2
system and nightly I run a process that, for each database, performs
first a "VACUUM ANALYZE;" then runs the vacuumlo on the same database.
The problem is that the "VACUUM ANALYZE;" results in a
ERROR: Memory exhausted in AllocSetAlloc(1048575996)
The (1048575996) doesn't change regardless of the database that the
vacuum is running on. Additionally, our tables in all of our databases
are reindexed every 6 hours.
That's the problem.
My current workaround is prior to the "VACUUM ANALYZE;" I drop all
indexes to all non-system, non-postgres tables, then perform the
vacuum on each non-system, non-postgres table, and finally recreate
the indexes. The reindex every 6 hours is currently disabled as well.
This is the only solution I have to date.
Any input would be greatly appreciated.
Greg
--
Greg Spiegelberg
Sr. Product Development Engineer
Cranel, Incorporated.
Phone: 614.318.4314
Fax: 614.431.8388
Email: gspiegelberg(at)Cranel(dot)com
Cranel. Technology. Integrity. Focus.
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2003-06-17 14:37:41 | Re: psql DBNAME -U USER (how to disable -U option?) |
Previous Message | scott.marlowe | 2003-06-17 14:13:46 | Re: psql DBNAME -U USER (how to disable -U option?) |