MIME-Version: 1.0
References: 
 <CAFOhELfb36xY8iDBGuqGwGau0cXV_ZxQhSoBp=WLF4fFadwahA@mail.gmail.com>
In-Reply-To: 
 <CAFOhELfb36xY8iDBGuqGwGau0cXV_ZxQhSoBp=WLF4fFadwahA@mail.gmail.com>
From: Dave Page <dpage@pgadmin.org>
Date: Fri, 4 Jan 2019 14:45:40 +0000
Message-ID: 
 <CA+OCxow7Rwu7YA45ZzE+XfX765iyuZP=+JwVHpqFsxJwmErnMg@mail.gmail.com>
Subject: Re: [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
To: Khushboo Vashi <khushboo.vashi@enterprisedb.com>
Cc: pgadmin-hackers <pgadmin-hackers@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Thanks, patch applied.

On Fri, Jan 4, 2019 at 11:53 AM Khushboo Vashi
<khushboo.vashi@enterprisedb.com> wrote:
>
> Hi,
>
> Please find the attached patch to fix RM #3702 - pgAdmin dashboard showin=
g the oid for the user-defined tables and table names for the catalog table=
s 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 th=
e server level.  The reason for this is, at the server level we fetch the d=
ata from the pg_locks with the maintenance database, so it can not fetch th=
e pg_class relation for the other database tables (relation::regclass).
>
> Please find the attached screen-shots for the issue and the fix and let m=
e know if there is any other way to fix this.
>
> Thanks,
> Khushboo
>
>


--=20
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company