| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Tomeh, Husam" <htomeh(at)firstam(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Vacuum - Out of memory |
| Date: | 2006-01-31 14:36:12 |
| Message-ID: | 3549.1138718172@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Tomeh, Husam" <htomeh(at)firstam(dot)com> writes:
> ThanksTom. I've asked the SA to bounce the server thinking it may be a
> memory fragmentation issue on the server. After bouncing the server, I
> was able to run vacuum successfully. (Before bouncing the server, I
> tried a lower value of maintenance_work_mem of 512MB and vacuum worked
> fine which made me feel better the status of data not being corrupted).
> Do you agree with me at this point that it's not a data corruption
> issue? Thanks again.
No, I don't, unless you have fields in the database that *should* be
1-billion-and-change bytes long.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Düster Horst | 2006-01-31 16:48:27 | query to select the table primary key column name |
| Previous Message | Tomeh, Husam | 2006-01-31 04:09:07 | Re: Vacuum - Out of memory |