X-Original-To: pgsql-performance-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 354089FA2E6
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 12 Jun 2006 02:56:34 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 06731-05 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 12 Jun 2006 02:56:25 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170])
	by postgresql.org (Postfix) with ESMTP id A28739FA38F
	for <pgsql-performance@postgresql.org>;
	Mon, 12 Jun 2006 02:56:25 -0300 (ADT)
Received: by ug-out-1314.google.com with SMTP id m2so2149454ugc
	for <pgsql-performance@postgresql.org>;
	Sun, 11 Jun 2006 22:56:23 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
	b=NlNEemGSSSaZe2K182fv4lH0qR+JNtends7jHtdw/8HsAdw0nFAmppBBXxdhpnddYnjVddItKJM9xHSB/Ur/0SMHmBwdyAZSl4We/NFesKs3pMtgDR83bfveULuqCVwMiw0Pu0gyptGRHHXss/pKmSiQHWs7pWKxxyJjh/cEmi8=
Received: by 10.66.216.20 with SMTP id o20mr4822496ugg;
	Sun, 11 Jun 2006 22:56:23 -0700 (PDT)
Received: by 10.66.222.12 with HTTP; Sun, 11 Jun 2006 22:56:23 -0700 (PDT)
Message-ID: <674d1f8a0606112256t71b38395gc894fcbca45afedc@mail.gmail.com>
Date: Mon, 12 Jun 2006 11:26:23 +0530
From: "Gourish Singbal" <gourish@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: pgsql_tmp and postgres settings
In-Reply-To: <20060609155953.GX45331@pervasive.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2517_10345714.1150091783502"
References: <20060609122948.6B7419FA621@postgresql.org>
	<20060609155953.GX45331@pervasive.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200606/126
X-Sequence-Number: 19483

------=_Part_2517_10345714.1150091783502
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Where is the pgsql_tmp folder present ?.  i am unable to see it in the data
directory of postgresql.

~gourish

On 6/9/06, Jim C. Nasby <jnasby@pervasive.com> wrote:
>
> On Fri, Jun 09, 2006 at 02:23:04PM +0200, Domenico - Sal. F.lli Riva
> wrote:
> > Hello,
> >
> > During insert or update, potgresql write in pgsql_tmp directory and so
> > performance are very poor.
>
> pgsql_tmp is used if a query runs out of work_mem, so you can try
> increasing that.
>
> > My configuration is:
> >
> > Work mem                    10240
> >
> > Effective_cache_size      30000
> You're off by a factor of 10.
>
> > Shared buffers              9000
> I'd suggest bumping that up to at least 30000.
>
> > Postgresql (RPM from official website) 8.1.0
>
> You should upgrade to 8.1.4. There's a number of data loss bugs waiting
> to bite you.
> --
> Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
> Pervasive Software      http://pervasive.com    work: 512-231-6117
> vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>               http://archives.postgresql.org
>



-- 
Best,
Gourish Singbal

------=_Part_2517_10345714.1150091783502
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>&nbsp;</div>
<div>Where is the pgsql_tmp folder present ?.&nbsp; i am unable to see it in the data directory of postgresql. </div>
<div>&nbsp;</div>
<div>~gourish<br>&nbsp;</div>
<div><span class="gmail_quote">On 6/9/06, <b class="gmail_sendername">Jim C. Nasby</b> &lt;<a href="mailto:jnasby@pervasive.com">jnasby@pervasive.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Fri, Jun 09, 2006 at 02:23:04PM +0200, Domenico - Sal. F.lli Riva wrote:<br>&gt; Hello,<br>&gt;<br>&gt; During insert or update, potgresql write in pgsql_tmp directory and so
<br>&gt; performance are very poor.<br><br>pgsql_tmp is used if a query runs out of work_mem, so you can try<br>increasing that.<br><br>&gt; My configuration is:<br>&gt;<br>&gt; Work mem&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;10240<br>&gt;<br>
&gt; Effective_cache_size&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;30000<br>You're off by a factor of 10.<br><br>&gt; Shared buffers&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9000<br>I'd suggest bumping that up to at least 30000.<br><br>&gt; Postgresql (RPM from official website) 8.1.0
<br><br>You should upgrade to 8.1.4. There's a number of data loss bugs waiting<br>to bite you.<br>--<br>Jim C. Nasby, Sr. Engineering Consultant&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:jnasby@pervasive.com">jnasby@pervasive.com</a><br>Pervasive Software&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a href="http://pervasive.com">http://pervasive.com</a>&nbsp;&nbsp;&nbsp;&nbsp;work: 512-231-6117<br>vcard: <a href="http://jim.nasby.net/pervasive.vcf">http://jim.nasby.net/pervasive.vcf</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; cell: 512-569-9461<br><br>---------------------------(end of broadcast)---------------------------
<br>TIP 4: Have you searched our list archives?<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="http://archives.postgresql.org">http://archives.postgresql.org</a><br></blockquote></div><br><br clear="all"><br>-- <br>Best,<br>Gourish Singbal 

------=_Part_2517_10345714.1150091783502--