pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Julius Tuskenis <julius@nsoft.lt>
To: pgsql-admin@postgresql.org
Subject: Re: possible memory leak in Server Status window
Date: Mon, 07 Feb 2011 16:23:36 +0200
Message-ID: <4D500068.8070707@nsoft.lt> (raw)
In-Reply-To: <4D4FD41E.2050909@nsoft.lt>
References: <4D4FADCA.6040604@nsoft.lt>
	<4D4FC0E6.7060302@lelarge.info>
	<4D4FD41E.2050909@nsoft.lt>

2011.02.07 13:14, Julius Tuskenis rašė:
> 2011.02.07 11:52, Guillaume Lelarge rašė:
>> Did you lower each report? because each individual report has its own 
>> timer.
>>
> I'm sorry, I have only one report (Server status window). When you say 
> "lower" do you mean "minimize" ? No, I have left it on screen. Or do 
> you mean refresh interval? As I have single server status window, 
> there is no window left with shorter interval.
>
> Could the answer be in Locks window? I noticed, that even when I set 
> refresh interval to 10min, lock list is updated after the interval of 
> approximately 1 minute. Is this expected behavior? And when having 
> refresh interval = 10min the events of increase to VM become rare. If 
> I hit refresh button - i can observe the increase.
>
> I still was not able to reproduce on other servers. Maybe it is 
> related to the error we found Friday night in System log "The server 
> was unable to allocate from the system nonpaged pool because the pool 
> was empty." I tried to google - found an explanation that this could 
> mean there is a memory leak in kernel or in drivers. Maybe something 
> is wrong in system... This is the first time I encounter such a problem.
>
I'm sorry - I guess I should ask for help in pgAdmin mailing list.

-- 
Julius Tuskenis
Programavimo skyriaus vadovas
UAB nSoft
mob. +37068233050




view thread (5+ messages)  latest in thread

Message-ID: <4D500068.8070707@nsoft.lt>
Permalink:  ../4D500068.8070707@nsoft.lt/
Also on:    postgresql.org/message-id/4D500068.8070707@nsoft.lt

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: julius@nsoft.lt
  Subject: Re: possible memory leak in Server Status window
  In-Reply-To: <4D500068.8070707@nsoft.lt>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox