Skip site navigation (1) Skip section navigation (2)

Re: Used Memory

From: "Christian Paul B(dot) Cosinas" <cpc(at)cybees(dot)com>
To: "'Mark Kirkwood'" <markir(at)paradise(dot)net(dot)nz>,<pgsql-performance(at)postgresql(dot)org>
Subject: Re: Used Memory
Date: 2005-10-25 03:20:09
Message-ID: 007801c5d913$018d2340$1e21100a@ghwk02002147 (view raw or flat)
Thread:
Lists: pgsql-performance
Hi mark

I have so many functions, more than 100 functions in the database :) And I
am dealing about 3 million of records in one database.
And about 100 databases :)


-----Original Message-----
From: Mark Kirkwood [mailto:markir(at)paradise(dot)net(dot)nz]
Sent: Tuesday, October 25, 2005 3:07 AM
To: Christian Paul B. Cosinas
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Used Memory

Christian Paul B. Cosinas wrote:
> Hi To all those who replied. Thank You.
> 
> I monitor my database server a while ago and found out that memory is 
> used extensively when I am fetching records from the database. I use 
> the command "fetch all" in my VB Code and put it in a recordset.Also 
> in this command the CPU utilization is used extensively.
> 
> Is there something wrong with my code or is it just the way postgresql 
> is behaving which I cannot do something about it?
> 
> I just monitor one workstation connecting to the database server and 
> it is already eating up about 20 % of the CPU of database server.
> 
> Which I think will not be applicable to our system since we have a 
> target of
> 25 PC connecting to the database server most of the time.
> 

Could you post the query and the output of EXPLAIN ANALYZE?

In addition, have you run ANALYZE on all the tables in that database ? 
(sorry, have to ask :-) ....).

cheers

Mark


I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html    


In response to

Responses

pgsql-performance by date

Next:From: Mark KirkwoodDate: 2005-10-25 04:14:35
Subject: Re: Used Memory
Previous:From: Mark KirkwoodDate: 2005-10-25 03:06:43
Subject: Re: Used Memory

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group