Just a random thought/question... Are you running else on the machine? When you say "resource usage", do you mean hd space, memory, processor, ??? What are your values in top? More info... Cheers Anton On 27/08/2007, Bill Moran <wmoran@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > In response to Chris Mair <chris@xxxxxxxx>: > > > > Hi, > > > > > > Note: I have already vacumm full. It does not solve the problem. > > To jump in here in Chris' defense, regular vacuum is not at all the same > as vacuum full. Periodic vacuum is _much_ preferable to an occasional > vacuum full. > > The output of vacuum verbose would have useful information ... are you > exceeding your FSM limits? > > Try a reindex on the database. There may be some obscure corner > cases where reindex makes a notable improvement in performance. > > > > I have a postgres 8.1 database. In the last days I have half traffic > > > than 4 weeks ago, and resources usage is twice. The resource monitor > > > graphs also shows hight peaks (usually there is not peaks) > > Resource monitor graphs? That statement means nothing to me, therefore > I don't know if the information they're providing is useful or accurate, > or even _what_ it is. What, exactly, are these graphs monitoring? > > You might want to provide your postgresql.conf. > > Have you considered the possibility that the database has simply got more > records and therefore access takes more IO and CPU? > > > > The performarce is getting poor with the time. > > > > > > Im not able to find the problem, seems there is not slow querys ( I have > > > log_min_duration_statement = 5000 right now, tomorrow I ll decrease it ) > > > > > > Server is HP, and seems there is not hardware problems detected. > > > > > > Any ideas to debug it? > > > > Hi, > > > > first of all: let us know the exact version of PG and the OS. > > > > If performance is getting worse, there ususally is some bloat > > envolved. Not vacuuming aggressivly enough, might be the most > > common cause. Do you autovacuum or vacuum manually? > > Tell us more... > > > > > > Bye, > > Chris. > > > > > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 3: Have you checked our extensive FAQ? > > > > http://www.postgresql.org/docs/faq > > > > > > > > > > > > > > > -- > Bill Moran > Collaborative Fusion Inc. > http://people.collaborativefusion.com/~wmoran/ > > wmoran@xxxxxxxxxxxxxxxxxxxxxxx > Phone: 412-422-3463x4023 > > **************************************************************** > IMPORTANT: This message contains confidential information and is > intended only for the individual named. If the reader of this > message is not an intended recipient (or the individual > responsible for the delivery of this message to an intended > recipient), please be advised that any re-use, dissemination, > distribution or copying of this message is prohibited. Please > notify the sender immediately by e-mail if you have received > this e-mail by mistake and delete this e-mail from your system. > E-mail transmission cannot be guaranteed to be secure or > error-free as information could be intercepted, corrupted, lost, > destroyed, arrive late or incomplete, or contain viruses. The > sender therefore does not accept liability for any errors or > omissions in the contents of this message, which arise as a > result of e-mail transmission. > **************************************************************** > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > -- echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc This will help you for 99.9% of your problems ... ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
