Re: pgsql_tmp and postgres settings - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: pgsql_tmp and postgres settings
Date
Msg-id 20060612151530.GR34196@pervasive.com
Whole thread Raw
In response to Re: pgsql_tmp and postgres settings  ("Gourish Singbal" <gourish@gmail.com>)
List pgsql-performance
On Mon, Jun 12, 2006 at 11:26:23AM +0530, Gourish Singbal wrote:
> Where is the pgsql_tmp folder present ?.  i am unable to see it in the data
> directory of postgresql.

It will be under the *database* directory, under $PGDATA/base. SELECT
oid,* FROM pg_database; will tell you what directory to look in for your
database.

> 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

--
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

pgsql-performance by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Posrgres speed problem
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Posrgres speed problem