Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 885C91337B92
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri, 29 Apr 2011 04:13:17 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 20522-01
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri, 29 Apr 2011 07:13:10 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from nm7.bullet.mail.ac4.yahoo.com (nm7.bullet.mail.ac4.yahoo.com
	[98.139.52.204])
	by mail.postgresql.org (Postfix) with SMTP id ECF4B1337B3E
	for <pgsql-performance@postgresql.org>;
	Fri, 29 Apr 2011 04:13:09 -0300 (ADT)
Received: from [98.139.52.196] by nm7.bullet.mail.ac4.yahoo.com with NNFMP;
	29 Apr 2011 07:13:08 -0000
Received: from [98.139.52.162] by tm9.bullet.mail.ac4.yahoo.com with NNFMP;
	29 Apr 2011 07:13:08 -0000
Received: from [127.0.0.1] by omp1045.mail.ac4.yahoo.com with NNFMP;
	29 Apr 2011 07:13:08 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 445265.18958.bm@omp1045.mail.ac4.yahoo.com
Received: (qmail 2265 invoked by uid 60001); 29 Apr 2011 07:13:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024;
	t=1304061188; bh=JlVXGMe7VlkKfxqNNurwr9PJzBwbDdXn1s7BnZAnzgc=;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
	b=qUFquQoeJfIS5hy6yNP8/IQ4+9J4lGPg2NdXDczqRvndoGkLHmp1pv39cyntdG7ymGwTG91P+Aj1gf3uugVklqAT/5w3FSmunjnTvKhlBGgOi+ya/KWbimsGw6j067Fpj9FU7mxGfvZoc7eNmj/Arr23W1glIG78e5vVFvvZ+qg=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
	b=yH2vefiByL7N/zyq2+HJrA0AF9EK2JaSYj1YKglXx2yCuQiVX/rkSjBJQ92YH/XCPnd7AVpg0YubTIDnYr4GpN71YC6+PJxChuVNPbpO5nidyv/+zLKFwD7ZwSG6wabFWTeuCb/IlN7vsDAGvRODrExgKLYY977lHlh2wodxMv8=;
Message-ID: <343857.89994.qm@web63001.mail.re1.yahoo.com>
X-YMail-OSG: 7h8GPeIVM1mF7p_Ac4sJsmGb2vcqhj6Hn.rXVBjoMp3Eaml
	Tqfh9UkzEg064_Kz9Rurn3m9WWPE.odqP_J5xy3KGob20RudzHry.8_AQ3D2
	ThGzV_xPZNGXtXWCRpkGnmwtiyh0nCnaUw2Ebf6v6VyQGqnfkWeXnqyJQ4Il
	I6g9bS5wqr84gvV6gH6kfDwVs4EAqJdICRJ3F.v3hJeQ0YURjY4pB6.T.8L7
	jhIMqUdxskZHfQfUrlOhvAA3Cu9V9ettW7x_1owbvx_afz.G.H5D0tH3Fc98
	oTz494EQLLctj_kX5QKElyHggW3.d5tD.dRGBrllyV7nJvWCOE33cZdweJMM
	UOYURVvW38jMJIuzsCV26VHGBsHSzNTvXLz463Tmu86Qn
Received: from [193.166.11.251] by web63001.mail.re1.yahoo.com via HTTP;
	Fri, 29 Apr 2011 00:13:08 PDT
X-Mailer: YahooMailWebService/0.8.110.299900
Date: Fri, 29 Apr 2011 00:13:08 -0700 (PDT)
From: Qiang Wang <forest_qiang@yahoo.com>
Reply-To: Qiang Wang <forest_qiang@yahoo.com>
Subject: Will shared_buffers crash a server
To: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1323482908-1304061188=:89994"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.907 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_NONE=-0.0001, RFC_ABUSE_POST=0.001,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201104/400
X-Sequence-Number: 43462

--0-1323482908-1304061188=:89994
Content-Type: text/plain; charset=us-ascii

Hei: 


We have PostgreSQL 8.3 running on Debian Linux server. We built an applicantion using PHP programming language and Postgres database. There are appoximatly 150 users using the software constantly. We had some performance degration before and after some studies we figured out we will need to tune PostgreSQL configurations. 


We have 10GB memory and we tuned PostgreSQL as follow:
- max_connection = 100
- effective_cache_size = 5GB
- shared_buffer = 2GB
- wal_buffer = 30MB
- work_mem = 50MB

However we suffered 2 times server crashes after tunning the configuration. Does anyone have any idea how this can happen?

BR 

Kevin Wang

--0-1323482908-1304061188=:89994
Content-Type: text/html; charset=us-ascii

<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>Hei: <br></div><div><br></div><div>We have PostgreSQL 8.3 running on Debian Linux server. We built an applicantion using PHP programming language and Postgres database. There are appoximatly 150 users using the software constantly. We had some performance degration before and after some studies we figured out we will need to tune PostgreSQL configurations. <br></div><div><br></div><div>We have 10GB memory and we tuned PostgreSQL as follow:</div><div>- max_connection = 100</div><div>- effective_cache_size = 5GB</div><div>- shared_buffer = 2GB</div><div>- wal_buffer = 30MB</div><div>- work_mem = 50MB</div><div><br></div><div>However we suffered 2 times server crashes after tunning the configuration. Does anyone have any idea how this can happen?</div><div><br></div><div>BR <br></div><div>Kevin Wang<br></div></div></body></html>
--0-1323482908-1304061188=:89994--