From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Dhanaraj M <Dhanaraj(dot)M(at)Sun(dot)COM> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Need a help - Performance issues |
Date: | 2006-05-10 20:39:25 |
Message-ID: | 20060510203925.GU99570@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
There is/was a pg_autotune project, but it was pretty rudamentary and
didn't work very well when I tried it circa 2001. Your best bet is
probably to either do a lot of research, or hire a consultant.
On Tue, May 09, 2006 at 05:34:26PM +0530, Dhanaraj M wrote:
> I am currently looking at some performance issues. Our product uses the
> postgres as the backend
> and it uses a huge storage space.
>
> Is there a script available, which does the following:
>
>
> 1. When you point it to a postgres installation, -> 1.the script first
> identifies what platform (solaris-sparc/solaris x86/ Niagara) it is
> running on,
> 2. walks through all known tuning parameters (in /etc/system and
> postgresql.conf) on the system
> 3. lists out what parameters are optimal/suboptimal for that
> platform, and makes recommendations.
> 4. identifies when the last vaccumdb /fullvacuum (and other such
> database health maintenance commands) were run
> 5. comments about the growth of certain tables/databases
>
>
> If any body has the scripts or can give some links which could be useful
> for our group.
>
>
>
> Thanks
> Dhanaraj
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-05-10 21:03:51 | Re: BEGIN inside transaction should be an error |
Previous Message | Alvaro Herrera | 2006-05-10 20:24:45 | Re: sblock state on FreeBSD 6.1 |