| From: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com> |
|---|---|
| To: | Nagaraj Raj <nagaraj(dot)sf(at)yahoo(dot)com> |
| Cc: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org>, Pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgAdmin is freezing |
| Date: | 2020-04-20 03:01:18 |
| Message-ID: | CAFOhELfxxLeeT60Jgcn1TnNYYZmF6QfLEUxhjA4mbOU5i79M5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers pgadmin-support |
Hi,
On Sat, Apr 18, 2020 at 1:41 AM Nagaraj Raj <nagaraj(dot)sf(at)yahoo(dot)com> wrote:
> Hi,
>
> pgAdmin is freezing for other activities when dropping any table or index
> if command is held because of any lock occurring. In this state unable to
> access any other objects like stats, SQL statements, descriptions or query
> tool for other objects. pgAdmin resume to start working fine after either releasing
> lock or killed the process in the server.
> Is it a bug or its know behavior of pgAdmin?
>
> If a particular table/index is locked and you are trying to fetch the
details for the same object then I think this is the expected behaviour but
at the same time if you can not access the details of the other database
objects then it's a bug.
Thanks,
Khushboo
> Currently, I'm using the latest version pgAdmin 4 v4.20.
>
>
>
> Thanks,
> Rj
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Khushboo Vashi | 2020-04-20 03:25:58 | Re: [pgAdmin][RM4946] Issue with temporary tables on commit drop as. |
| Previous Message | Libor M. | 2020-04-19 12:20:39 | Re: pgAdmin 4 - next gettext usage fixes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashesh Vashi | 2020-04-20 03:04:50 | Re: Triggers and Full Text Search |
| Previous Message | Malik Rumi | 2020-04-20 02:40:39 | Triggers and Full Text Search |