>>> On Tue, Oct 16, 2007 at 3:43 PM, in message
<[EMAIL PROTECTED]>, "ssurui"
<[EMAIL PROTECTED]> wrote:
> use top command observe the available memory
top is not the best way to look at RAM usage. Try free or other tools.
> I find about 500MB memory is
> vanished after the SQL is executed
I'm not so sure you are correctly interpreting the memory information
provided by "top". In a virtual memory system, it is not uncommon
for the amount of RAM in use to cycle up and down, as programs grab
and release memory, and the system reclaims free memory as needed,
but not necessarily
The following bug has been logged online:
Bug reference: 3680
Logged by: ssurui
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Redhat LINUX Advance server 3
Description:memory leak when excuting a SQL "select count(id) from
chinatelecom;"
The following bug has been logged online:
Bug reference: 3679
Logged by: thobiyas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: windows xp
Description:need windows version
Details:
i would like have postgres
---(
Simon Riggs wrote:
> On Mon, 2007-10-15 at 22:54 +0100, Dave Page wrote:
>
>> A change has been applied for GP compatibility. It will be in pgAdmin 1.8.
>
> Wow Dave, that was quick! It was the right place after all. :-)
>
I exchanged a couple of emails with Luke a day or two back :-)
/D
