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 and Create Index
Date: Tue, 14 Feb 2006 18:49:18 -0500
Message-ID: <24285.1139960958@sss.pgh.pa.us> (raw)
In-Reply-To: <CB0FB369FF86E248A884BCC002562BCB010C0B01@pisgsna01sxch01.ana.firstamdata.com>
References: <CB0FB369FF86E248A884BCC002562BCB010C0B01@pisgsna01sxch01.ana.firstamdata.com>
"Tomeh, Husam" <htomeh@firstam.com> writes:
> mtrac=# show maintenance_work_mem ;
> maintenance_work_mem
> ----------------------
> 1048576 <======
> (1 row)
> mtrac=#
> mtrac=#
> mtrac=# create index mort_ht on mortgage(county_id,mtg_rec_dt);
> ERROR: out of memory <===
> DETAIL: Failed on request of size 134217728. <===
It would be useful to look at the detailed allocation info that this
(should have) put into the postmaster log. Also, if you could get
a stack trace back from the error, that would be even more useful.
To do that,
* start psql
* determine PID of connected backend (use pg_backend_pid())
* in another window, as postgres user,
gdb /path/to/postgres backend-PID
gdb> break errfinish
gdb> cont
* issue failing command in psql
* when breakpoint is reached,
gdb> bt
... stack trace printed here ...
gdb> q
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 and Create Index
In-Reply-To: <24285.1139960958@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