Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id ABF5F9FB6FC for ; Tue, 27 Mar 2007 21:51:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 72698-01 for ; Tue, 27 Mar 2007 21:51:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 751499FB6DB for ; Tue, 27 Mar 2007 21:51:48 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l2S0plJQ012361; Tue, 27 Mar 2007 20:51:47 -0400 (EDT) To: "Alexander B." cc: "pgsql-admin@postgresql.org" Subject: Re: Strange behavior In-reply-to: <46097157.3040100@yahoo.com.br> References: <46097157.3040100@yahoo.com.br> Comments: In-reply-to "Alexander B." message dated "Tue, 27 Mar 2007 16:32:39 -0300" Date: Tue, 27 Mar 2007 20:51:47 -0400 Message-ID: <12360.1175043107@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/215 X-Sequence-Number: 25039 "Alexander B." writes: > some developers were using the database, and suddenly no one could connect. Sounds like your postmaster process died. > Using PostgreSQL 8.1.4 on x86_64-pc-linux-gnu, compiled by GCC cc (GCC) > 3.3.5 (Debian 1:3.3.5-13) On Linux the most common reason for this has been that the kernel OOM killer decides to pick on the postmaster. Try to disable memory overcommit. It's rumored that having too little swap space may result in the OOM killer firing even when overcommit is off, too. regards, tom lane