Vacuum & Memory Exhausted error

Поиск
Список
Период
Сортировка
От Greg Spiegelberg
Тема Vacuum & Memory Exhausted error
Дата
Msg-id 3EEF26CC.9020102@cranel.com
обсуждение исходный текст
Ответы Re: Vacuum & Memory Exhausted error  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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@Cranel.com
Cranel. Technology. Integrity. Focus.



В списке pgsql-admin по дате отправления:

Предыдущее
От: "scott.marlowe"
Дата:
Сообщение: Re: psql DBNAME -U USER (how to disable -U option?)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Vacuum & Memory Exhausted error