X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 53580528B7 for ; Fri, 10 Jun 2005 14:16:16 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 89403-01 for ; Fri, 10 Jun 2005 17:16:15 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8A0855287A for ; Fri, 10 Jun 2005 14:16:14 -0300 (ADT) 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 j5AHFpo1023837; Fri, 10 Jun 2005 13:15:51 -0400 (EDT) To: "Lee Wu" Cc: "Steve Crawford" , pgsql-admin@postgresql.org Subject: Re: select * and save into a text file failed In-reply-to: References: Comments: In-reply-to "Lee Wu" message dated "Fri, 10 Jun 2005 11:03:56 -0600" Date: Fri, 10 Jun 2005 13:15:51 -0400 Message-ID: <23836.1118423751@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/80 X-Sequence-Number: 17835 "Lee Wu" writes: > either > 1. out of memory for query result > 2. killed > 3. crash PG Cases 2 and 3 represent the kernel out-of-memory code going nuts. Google for "OOM kill" and "memory overcommit". IMHO you never want Linux's default memory overcommit behavior on a production server. regards, tom lane