Re: pgsql_tmp and postgres settings

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: "Domenico - Sal(dot) F(dot)lli Riva" <domenico(dot)mozzanica(at)fratelliriva(dot)it>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: pgsql_tmp and postgres settings
Date: 2006-06-09 15:59:53
Message-ID: 20060609155953.GX45331@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim C. Nasby 2006-06-09 19:41:16 pg_xlog on data partition with BBU RAID
Previous Message Jim C. Nasby 2006-06-09 15:54:02 Re: Why date index is not used