Thanks to input Bruce M., figured out my performance problems - had to do
with a few QUERIES FROM HELL! After running EXPLAIN a few times I fine
tuned some of the worst ones, mostly over use of sub queries. Still
combing through my query log.
Getting there...
-r
---
Outgoing mail is certi
Lamar Owen <[EMAIL PROTECTED]> writes:
> Ryan Mahoney wrote:
> > Any input would be helpful! If you need additional info let me know.
>
> > BTW, Thanks to Lamar for some great tips today!
>
> You're more than welcome.
>
> I forgot a basic tip, which leads to a question:
> How often are you r
Ryan Mahoney wrote:
> Any input would be helpful! If you need additional info let me know.
> BTW, Thanks to Lamar for some great tips today!
You're more than welcome.
I forgot a basic tip, which leads to a question:
How often are you running VACUUM ANALYZE?
If this were PostgreSQL 7.0.3, we
I hope you have those postmasters listening on different ports.
> Here is some output from top...
>
> 9:20pm up 40 min, 1 user, load average: 3.77, 3.12, 3.74
> 41 processes: 36 sleeping, 5 running, 0 zombie, 0 stopped
> CPU states: 99.2% user, 0.7% system, 0.0% nice, 0.0% idle
> Mem: 5
Here is some output from top...
9:20pm up 40 min, 1 user, load average: 3.77, 3.12, 3.74
41 processes: 36 sleeping, 5 running, 0 zombie, 0 stopped
CPU states: 99.2% user, 0.7% system, 0.0% nice, 0.0% idle
Mem: 515664K av, 303712K used, 211952K free, 37476K shrd, 39552K buff
Swap: 5
I am running Postgresql 7.1 on a dedicated Redhat 7.0 box with 512meg ram
and an IDE hard drive.
All day long queries that usually seem to execute instantaneously have been
taking up to 10 second to run! I generally have about 6 postmasters
running, utilizing anywhere from 1% to 96% CPU utili
