| From: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com> |
|---|---|
| To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | [pgAdmin4][Patch]: RM 3702 - pgAdmin dashboard showing the oid for the user-defined tables and table names for the catalog tables in locks monitoring window |
| Date: | 2019-01-04 09:18:43 |
| Message-ID: | CAFOhELfb36xY8iDBGuqGwGau0cXV_ZxQhSoBp=WLF4fFadwahA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi,
Please find the attached patch to fix RM #3702 - pgAdmin dashboard showing
the oid for the user-defined tables and table names for the catalog tables
in locks monitoring window.
Dashboard > Server Activity > Locks - shows the table oid in the 'Target
relation' column instead of table name.
The attached patch fixes this issue for the database level but not for the
server level. The reason for this is, at the server level we fetch the
data from the pg_locks with the maintenance database, so it can not fetch
the pg_class relation for the other database tables (relation::regclass).
Please find the attached screen-shots for the issue and the fix and let me
know if there is any other way to fix this.
Thanks,
Khushboo
| Attachment | Content-Type | Size |
|---|---|---|
| Table_lock_after.png | image/png | 1.0 MB |
| Table_lock_before.png | image/png | 442.7 KB |
| RM_3702.patch | application/octet-stream | 2.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2019-01-04 09:23:10 | Re: pgAdmin 4 commit: Improvement in the look and feel of the whole applica |
| Previous Message | Aditya Toshniwal | 2019-01-04 04:51:25 | Re: pgAdmin 4 commit: Improvement in the look and feel of the whole applica |
