From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomeh, Husam <htomeh@firstam.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 0ut of Memory Error during Vacuum Analyze
Date: Tue, 14 Feb 2006 12:50:47 -0500
Message-ID: <19986.1139939447@sss.pgh.pa.us> (raw)
In-Reply-To: <CB0FB369FF86E248A884BCC002562BCB010C0AFB@pisgsna01sxch01.ana.firstamdata.com>
References: <CB0FB369FF86E248A884BCC002562BCB010C0AFB@pisgsna01sxch01.ana.firstamdata.com>
"Tomeh, Husam" <htomeh@firstam.com> writes:
> =# vacuum analyze code;
> ERROR: out of memory
> DETAIL: Failed on request of size 1073741820.
That looks a whole lot like a corrupt-data issue. The apparent
dependency on maintenance_work_mem is probably illusory --- I suspect
some of your trials are selecting the corrupted row to use in the
ANALYZE stats, and others are randomly selecting other rows.
If you are able to pg_dump the table in question then this theory is
wrong, but I'd suggest trying that first.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, htomeh@firstam.com
Subject: Re: 0ut of Memory Error during Vacuum Analyze
In-Reply-To: <19986.1139939447@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox