Re:

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Vivek Khera <vivek(at)khera(dot)org>, Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re:
Date: 2006-02-25 03:42:39
Message-ID: 200602250342.k1P3gdj15861@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


See the FAQ.

---------------------------------------------------------------------------

Jim C. Nasby wrote:
> On Thu, Feb 23, 2006 at 09:38:25AM -0500, Vivek Khera wrote:
> >
> > On Feb 22, 2006, at 10:44 PM, Chethana, Rao ((IE10)) wrote:
> >
> > >That is what I wanted to know, how do I tune it?
> >
> > If there were a simple formula for doing it, it would already have
> > been written up as a program that runs once you install postgres.
> >
> > You have to monitor your usage, use your understanding of your
> > application, and the Postgres manual to see what things to adjust.
> > It differs if you are CPU bound or I/O bound.
> >
> > And please keep this on list.
>
> FWIW, had you included a bit more of the original post others might have
> been able to provide advice... but now I have no idea what the original
> question was (of course a blank subject doesn't help either... no idea
> where that happened).
>
> --
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

  • Re: at 2006-02-23 20:29:05 from Jim C. Nasby

Browse pgsql-performance by date

  From Date Subject
Next Message Luke Lonergan 2006-02-25 04:41:52 Re: Reliability recommendations
Previous Message Mark Kirkwood 2006-02-25 01:18:31 Re: Reliability recommendations