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.
__
Husam Tomeh
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Monday, January 30, 2006 6:01 PM
To: Tomeh, Husam
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Vacuum - Out of memory
"Tomeh, Husam" <htomeh@firstam.com> writes:
> Any idea why I'm getting out-of-memory error?
Looks like a corrupt-data problem, but it's hard to tell any more than
that with only this much info. If it affects all tables then the
corruption is probably in a system catalog rather than every one of
the tables. You might try setting a breakpoint at errfinish to get
a stack trace from the point of the error; that would give us at least
a bit of a clue where the problem is.
regards, tom lane
**********************************************************************
This message contains confidential information intended only for the use of the addressee(s) named above and may
containinformation that is legally privileged. If you are not the addressee, or the person responsible for delivering
itto the addressee, you are hereby notified that reading, disseminating, distributing or copying this message is
strictlyprohibited. If you have received this message by mistake, please immediately notify us by replying to the
messageand delete the original message immediately thereafter.
Thank you.
FADLD Tag
**********************************************************************
