Re: out of memory error when running DB maintenance
От | Ben Deneweth |
---|---|
Тема | Re: out of memory error when running DB maintenance |
Дата | |
Msg-id | 4D0CF2BF.3050703@gmail.com обсуждение исходный текст |
Ответ на | Re: out of memory error when running DB maintenance (Guillaume Lelarge <guillaume@lelarge.info>) |
Список | pgadmin-support |
I am running Postgresql 8.3 Here are the last few lines of the pgAdmin output: DETAIL: 0 index row versions were removed. 0 index pages have been deleted, 0 are currently reusable. CPU 0.00s/0.00u sec elapsed 0.00 sec.INFO: "tourneyplayerdata": found 0 removable, 13226 nonremovable row versions in 151 pages DETAIL: 0 dead row versions cannot be removed yet. There were 217 unused item pointers. 1 pages contain useful free space. 0 pages are entirely empty. CPU 0.01s/0.00u sec elapsed 0.31 sec.INFO: analyzing "public.tourneyplayerdata"INFO: "tourneyplayerdata": scanned 151 of 151 pages, containing 13226 live rows and 0 dead rows; 3000 rows in sample, 13226 estimated total rowsINFO: vacuuming "public.compiledplayerresults_month" ERROR: out of memory DETAIL: Failed on request of size 534864402. ERROR: out of memory DETAIL: Failed on request of size 534864402. Thanks for any help. On 12/18/2010 2:08 AM, Guillaume Lelarge wrote: > Le 18/12/2010 06:14, Ben Deneweth a écrit : >> I have a DB taking up 220gb of a 300gb drive so I purged some old data >> from it. When I try to vaccum/analyze using pgAdmin III I keep getting >> an out of memory error. I am running Windows Vista 64 bit with 8gb of >> RAM and I have change the postgresql.conf file variables to the following: >> >> #custom_variable_classes = '' # list of custom variable class names >> shared_buffers = 1024MB >> effective_cache_size = 2048MB >> work_mem = 64MB >> maintenance_work_mem = 1024MB >> commit_delay = 10000 >> checkpoint_segments = 128 >> checkpoint_completion_target = 0.9 >> wal_buffers = 2MB >> >> Any ideas on how I can avoid running out of memory and run a successful >> vacuum/analyze? >> > Can you show us the complete error message? and tell us what PostgreSQL > release you use? > >
В списке pgadmin-support по дате отправления: