AW: table lookup for pg_stat_progress_vacuum doesn't work

From: <Uwe(dot)deReuter(at)t-systems(dot)com>
To: <laurenz(dot)albe(at)cybertec(dot)at>, <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: AW: table lookup for pg_stat_progress_vacuum doesn't work
Date: 2020-12-16 07:56:46
Message-ID: FR2P281MB0156953BFB6780A096D15BA5D3C50@FR2P281MB0156.DEUP281.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Yes, good point.
I was on a wrong track as pg_stat_progress_vacuum is global.
I found it now.
Many thanks.

Best regards
Uwe de Reuter

-----Ursprüngliche Nachricht-----
Von: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Gesendet: Mittwoch, 16. Dezember 2020 08:31
An: de Reuter, Uwe <Uwe(dot)deReuter(at)t-systems(dot)com>; pgsql-admin(at)lists(dot)postgresql(dot)org
Betreff: Re: table lookup for pg_stat_progress_vacuum doesn't work

On Wed, 2020-12-16 at 07:25 +0000, Uwe(dot)deReuter(at)t-systems(dot)com wrote:
> We want to lookup the table name for entries we see in pg_stat_progress_vacuum.
> When we do this based on relid from pg_stat_progress_vacuum we don’t
> find an entry in the pg_class table (no match where pg_stat_progress_vacuum.relid=pg_class.oid).
> Should that happen at all and where can I do the lookup if not in pg_class ?

The table is probably in a database different from the one you are connected to.
Look at the "datname" column.

Every database has its own catalog tables.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Yambu 2020-12-16 12:01:13 Encrypt data in column
Previous Message Laurenz Albe 2020-12-16 07:31:02 Re: table lookup for pg_stat_progress_vacuum doesn't work