With reduced logging, I still get regular periods of unresponsiveness, even when Don't Refresh is set in the monitor window.
Does PgAdmin look at all logs in pg_log, or only the current one? Is there a way to disable log monitoring, as a test for the cause of this issue? >________________________________ > From: MattK <mk...@yahoo.com> >To: Dave Page <dp...@pgadmin.org> >Cc: "pgadmin-support@postgresql.org" <pgadmin-support@postgresql.org> >Sent: Tuesday, March 20, 2012 12:54 PM >Subject: Re: [pgadmin-support] Server status hanging on OS X > > >Very likely. I had some large log files (>1GB). Setting the log rotation size >to 100MB seems to have brought my the server status monitor back to life. > > >Thanks! > > > >>________________________________ >> From: Dave Page <dp...@pgadmin.org> >>To: MattK <mk...@yahoo.com> >>Cc: "pgadmin-support@postgresql.org" <pgadmin-support@postgresql.org> >>Sent: Tuesday, March 20, 2012 4:47 AM >>Subject: Re: [pgadmin-support] Server status hanging on OS X >> >>On Mon, Mar 19, 2012 at 7:26 PM, MattK <mk...@yahoo.com> wrote: >>> I can reproduce the issue in v1.14.0 and v1.14.1 as well. This does not >>> happen on all of my Postgres instances, the one I am trying to actively >>> monitor that exhibits the problem is through the ssh port forward. >>> >>> Running ssh -v -L 5433:<server>:5432 <user>@<server> seems to show a >>> constant traffic stream, with messages like this repeating: >>> >>> debug2: channel 5: window 1997018 sent adjust 100134 >>> debug2: channel 5: window 1997018 sent adjust 100134 >>> debug2: channel 5: window 1997018 sent adjust 100134 >>> debug2: channel 5: window 1997018 sent adjust 100134 >>> debug2: channel 5: window 1997018 sent adjust 100134 >>> debug2: channel 5: window 1997018 sent adjust 100134 >> >>Could it be trying to load a very large log file? >> >>-- >>Dave Page >>Blog: http://pgsnake.blogspot.com >>Twitter: @pgsnake >> >>EnterpriseDB UK: http://www.enterprisedb.com >>The Enterprise PostgreSQL Company >> >> >> > >
