AW: table lookup for pg_stat_progress_vacuum doesn't work
От | |
---|---|
Тема | AW: table lookup for pg_stat_progress_vacuum doesn't work |
Дата | |
Msg-id | FR2P281MB0156953BFB6780A096D15BA5D3C50@FR2P281MB0156.DEUP281.PROD.OUTLOOK.COM обсуждение исходный текст |
Ответ на | Re: table lookup for pg_stat_progress_vacuum doesn't work (Laurenz Albe <laurenz.albe@cybertec.at>) |
Список | 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.albe@cybertec.at> Gesendet: Mittwoch, 16. Dezember 2020 08:31 An: de Reuter, Uwe <Uwe.deReuter@t-systems.com>; pgsql-admin@lists.postgresql.org Betreff: Re: table lookup for pg_stat_progress_vacuum doesn't work On Wed, 2020-12-16 at 07:25 +0000, Uwe.deReuter@t-systems.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
В списке pgsql-admin по дате отправления: