Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dwuiK-0001fY-9G for pgadmin-support@arkaria.postgresql.org; Tue, 26 Sep 2017 18:36:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dwuiJ-0006CZ-OL for pgadmin-support@arkaria.postgresql.org; Tue, 26 Sep 2017 18:36:11 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dwuiJ-0006CP-H7 for pgadmin-support@lists.postgresql.org; Tue, 26 Sep 2017 18:36:11 +0000 Received: from sonic310-21.consmr.mail.gq1.yahoo.com ([98.137.69.147]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dwuiG-0003W9-7Z for pgadmin-support@postgresql.org; Tue, 26 Sep 2017 18:36:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1506450966; bh=em3XlrSVTHiUAeyXtzncv+OsJNkqbJP1IlHLraCRReQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=QUQzGfHYsjh8b8NbX1kB+IQ7PEE27wTr5i6n4Zt4DoXxczNUtOpbSX8Mr1d7bXWEAoj12zKLCuPHGeSoQ7gSsJg1R5iugCCU8QHwVx3EMnsFj+3zX4/ZiUOGDmh2UKM8NJ8O9zi3f4RlXfCOpvIvxh0orACV2N3S0kicIzQdRxxMOeYVTVoMvgW4ybs33Z1c/uFsk2gTAKHQUxItXDIW+wJwdSs+poyHJRw7YBCE5QdPKo8vLp5mbz6lzcpuxVTdoIMfAWYxuTw3hZB6q5RoiDbWm/6SqUl/kkJSDOt23L9EGV2hIAWQOEP9UrQPHb90bFpVJS4cEAgP9xe9IzJmdw== X-YMail-OSG: xNJILIgVM1kcBMOvViCybgXjE8bLSG1QTlMwJnbQ3gH_NuI5CtmxFRMRA7daJr6 gjFCmRT_1Am9RXHA7AGOo9nZpaU0sc7nxK8vFD9vQPkj6bV_kkRNc6xjjpZdOlL2FxCFjMW304NJ _gS4_uJIm7oOQcjsuIFTOnyKWFgRFRUErlWfMvpoyvvPUORYHFDuj1XLgzFZi1JfU_rOeWeDlLBe s3rQ7k1o97wOO9cCUfXuVhQvGMSRP8LvuFajxzcbZ01UoAfseOcxAa0odzC2ptdPTdBx_oUY0XeY ucaxy56kRu9DHb9gHaMf8ipbt30Kh2dPqYuzNjCKwFqLaCRooxx.5xV6VEqqndGSHqnBbHnQNXyw NsDgdNE_WMJsaS02kNwAEYVDii5KxQ4EINzxloHSI_cB7MjbrPiPHJYfDN1tzi3mWdCj66fQe3xr Xq63olLNhFsqDy5dEa3pUhqjmo_qh7UQfQ1Z8icyzZA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Tue, 26 Sep 2017 18:36:06 +0000 Date: Tue, 26 Sep 2017 18:35:55 +0000 (UTC) From: Melvin Davidson Reply-To: Melvin Davidson To: Murtuza Zabuawala Cc: PgAdmin Support Message-ID: <241677128.9738436.1506450955042@mail.yahoo.com> In-Reply-To: References: <72477705.9257896.1506393191292.ref@mail.yahoo.com> <72477705.9257896.1506393191292@mail.yahoo.com> <2122123787.9522222.1506433270904@mail.yahoo.com> Subject: Re: pgAdmin 4 v2.0 Release Candidate 2 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9738435_361670990.1506450955040" X-Mailer: WebService/1.1.10521 YMailNorrin Mozilla/5.0 (Windows NT 10.0; rv:55.0) Gecko/20100101 Firefox/55.0 Content-Length: 2834 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Unsubscribe: , List-Archive: Precedence: bulk ------=_Part_9738435_361670990.1506450955040 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I noticed that the dashboard has is not in the server panel by default,but = must be added. Was that intentional? Also, in PgAdmin III, it was possible to select and cancel session(s).Howev= er, in PgAdmin4 sessions can no longer be canceled/killed from the dashboar= d, only the associated transaction. That is a major change. As a DBA, I nee= d to be able to kill _sessions_. I can get around that withSQL, but WHY the= change? Please, STOP changing how PgAdmin works! Melvin Davidson =F0=9F=8E=B8 I reserve the right to fantasize.=C2=A0 Whether or not you=20 wish to share my fantasy is entirely up to you.=20 www.youtube.com/unusedhero/videos Folk Alley - All Folk - 24 Hours a day=20 www.folkalley.com ------=_Part_9738435_361670990.1506450955040 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I noticed that th= e dashboard has is not in the server panel by default,
but= must be added. Was that intentional?

<= b>Also, in PgAdmin III, it was possible to select and cancel session(s).
However, in PgAdmin4 sessions can no longer be canceled/kill= ed from the dashboard, only the associated transaction. That is a major cha= nge. As
a DBA, I need to be able to kill _sessions_. I ca= n get around that with
SQL, but WHY the change? Please, ST= OP changing how PgAdmin works!

Melvin Davidson =F0=9F=8E=B8
I reserve the right to fantasize.  Whether or not you
wish= to share my fantasy is entirely up to you.
www.youtube.com/unusedhero/videos=
Folk Alley - All Folk - 24 Hours a day
www.folkalley.com

=

------=_Part_9738435_361670990.1506450955040--