From: | Alban Hertroys <alban(dot)hertroys(at)apollovredestein(dot)com> |
---|---|
To: | pgadmin-support(at)postgresql(dot)org |
Subject: | Dashboard gets stuck |
Date: | 2017-08-28 14:03:34 |
Message-ID: | OF3434C36D.365679CD-ONC125818A.004B7932-C125818A.004D3B24@apollotyres.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
I'm running pgAdmin v1.6 on Windows 7 (64-bit). I'm monitoring a
long-running ETL job that inserts batches of records into PG 9.6 on Linux
(CentOS 7). The dashboard gives a nice view of how things are going.
Unfortunately, at random moments random graphs seem to get stuck and no
longer update. The 'Tuples In' graph seems the most vulnerable to that
ailment, and it's just the one that I need most, while the 'Transactions
per second' seems the most stable of the bunch.
There doesn't seem to be a way to 'unstuck' the graphs except for closing
and restarting pgAdmin.
Alban Hertroys.
Alban Hertroys
D: | T: +31 (0)53 4888 888 | E: alban(dot)hertroys(at)apollovredestein(dot)com
Apollo Vredestein B.V.| Ir. E.L.C. Schiffstraat 370, 7547 RD Enschede, The
Netherlands
Chamber of Commerce number: 34223268
The information contained in this e-mail is intended solely for the use of the
individual or entity to whom it is addressed. If you are not the intended
recipient, you are hereby notified that any disclosure, copying, distribution
or action in relation to the contents of this information is strictly
prohibited and may be unlawful and request you to delete this message and any
attachments and advise the sender by return e-mail. The confidentiality of this
message is not warranted. Apollo Vredestein and its subsidiaries rule out any
and every liability resulting from this or any other electronic transmission
Please consider the environment before printing this e-mail
From | Date | Subject | |
---|---|---|---|
Next Message | Brainco AG | 2017-08-29 11:02:48 | MAcOS will not accept that pgadmin |
Previous Message | Thom Brown | 2017-08-25 13:23:56 | Re: ? bug pg 9.6 |