X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 8AFF19DC80F for ; Tue, 14 Feb 2006 19:49:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 97961-06 for ; Tue, 14 Feb 2006 19:49:22 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 713159DC955 for ; Tue, 14 Feb 2006 19:49:16 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k1ENnIDW024286; Tue, 14 Feb 2006 18:49:18 -0500 (EST) To: "Tomeh, Husam" cc: pgsql-performance@postgresql.org Subject: Re: 0ut of Memory Error during Vacuum Analyze and Create Index In-reply-to: References: Comments: In-reply-to "Tomeh, Husam" message dated "Tue, 14 Feb 2006 15:40:17 -0800" Date: Tue, 14 Feb 2006 18:49:18 -0500 Message-ID: <24285.1139960958@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.109 required=5 tests=[AWL=0.109] X-Spam-Score: 0.109 X-Spam-Level: X-Archive-Number: 200602/186 X-Sequence-Number: 17172 "Tomeh, Husam" 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