| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Spiegelberg <gspiegelberg(at)cranel(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Vacuum & Memory Exhausted error |
| Date: | 2003-06-17 16:13:14 |
| Message-ID: | 13376.1055866394@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Greg Spiegelberg <gspiegelberg(at)cranel(dot)com> writes:
> The problem is that the "VACUUM ANALYZE;" results in a
> ERROR: Memory exhausted in AllocSetAlloc(1048575996)
If you do VACUUM and ANALYZE separately, which part shows the failure?
(I'm betting on ANALYZE.) And have you narrowed down which table it
fails on? (Adding the VERBOSE option would let you track that.)
This looks to me like a data-corruption problem, specifically a bad
value of the length word in a variable-length field. (Adjacent data
is probably clobbered too, but the length problem is showing itself
first.) See previous threads in the archives for general advice about
tracking down broken rows and getting rid of them.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Donald Fraser | 2003-06-17 16:58:24 | Redhat 9.0 |
| Previous Message | scott.marlowe | 2003-06-17 14:37:41 | Re: psql DBNAME -U USER (how to disable -U option?) |