| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)yahoo(dot)com> |
| Cc: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>, PgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: pgAdmin 4 v2.0 Release Candidate 2 |
| Date: | 2017-09-26 19:14:28 |
| Message-ID: | 01D2F330-4600-4382-B33F-4D92BB12D23F@pgadmin.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
> On 26 Sep 2017, at 19:35, Melvin Davidson <melvin6925(at)yahoo(dot)com> wrote:
>
> I noticed that the dashboard has is not in the server panel by default,
> but must be added. Was that intentional?
What does that mean?
>
> Also, in PgAdmin III, it was possible to select and cancel session(s).
> However, in PgAdmin4 sessions can no longer be canceled/killed from the dashboard, only the associated transaction. That is a major change.
pgAdmin 4 never did that. It’s not a change.
> As
> a DBA, I need to be able to kill _sessions_. I can get around that with
> SQL, but WHY the change? Please, STOP changing how PgAdmin works!
Query cancellation was a feature that was added in response to user requests. Are you really asking us to stop adding new features?
>
> Melvin Davidson 🎸
> 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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2017-09-26 19:36:34 | Re: pgAdmin 4 v2.0 Release Candidate 2 |
| Previous Message | Melvin Davidson | 2017-09-26 18:35:55 | Re: pgAdmin 4 v2.0 Release Candidate 2 |