From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | frank(dot)buettner(at)mdc-berlin(dot)de |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15493: Wrong name of fields/missing fields for the internal statistic |
Date: | 2018-11-08 14:48:11 |
Message-ID: | 19084.1541688491@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> After some times, many errors are logged about not existing fields.
> < 2018-11-08 14:21:59.820 CET >ERROR: column "procpid" does not exist at
> character 132
> < 2018-11-08 14:21:59.820 CET >STATEMENT: SELECT datname, datid, usename,
> client_addr, '' AS state, COALESCE(ROUND(EXTRACT(epoch FROM
> now()-query_start)),0) AS seconds,
> procpid as pid, regexp_replace(current_query, E'[\n\r\u2028]+', '
> ', 'g' ) AS current_query FROM pg_stat_activity WHERE (query_start IS NOT
> NULL AND current_query NOT LIKE '<IDLE>%') ORDER BY query_start, procpid
> DESC;
The procpid and current_query columns disappeared from pg_stat_activity in
Postgres 9.2 (or more accurately, they were renamed because they changed
meaning a bit). Apparently you're using some very old monitoring software
that hasn't been updated to know about that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-11-08 15:51:54 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
Previous Message | Jeff Janes | 2018-11-08 14:37:14 | Re: BUG #15493: Wrong name of fields/missing fields for the internal statistic |