BUG #17645: Strange queries that stuck in database system

Lists: pgsql-bugs
From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: thien(dot)phan(at)apollo(dot)edu(dot)vn
Subject: BUG #17645: Strange queries that stuck in database system
Date: 2022-10-16 23:43:24
Message-ID: 17645-7cbc0f9bf94bb2a6@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17645
Logged by: Thien, Phan Phuoc
Email address: thien(dot)phan(at)apollo(dot)edu(dot)vn
PostgreSQL version: 14.0
Operating system: Windows Server 2012 R2
Description:

Hi,

When I run this query

SELECT NOW() - query_start AS elapsed, pid, client_addr, query,
query_start, *
FROM pg_stat_activity
WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%'
ORDER BY query_start DESc;

I noticed that there are many queries (as below) that create many Windows
processes and CPU is 100%. Is it a bug? Please help!
Thank you very much!
Thien Phan

-- Load field definitions for (free-standing) composite types

SELECT typ.oid, att.attname, att.atttypid

FROM pg_type AS typ

JOIN pg_namespace AS ns ON (ns.oid = typ.typnamespace)

JOIN pg_class AS cls ON (cls.oid = typ.typrelid)

JOIN pg_attribute AS att ON (att.attrelid = typ.typrelid)

WHERE

(typ.typtype = 'c' AND cls.relkind='c') AND

attnum > 0 AND -- Don't load system attributes

NOT attisdropped

ORDER BY typ.oid, att.attnum
2022-10-17 00:01:21.117 +07 [[unknown]][4800][apollo_portal] FATAL:
terminating connection due to administrator command
2022-10-17 00:01:21.117 +07 [[unknown]][4800][apollo_portal] STATEMENT: --
Load field definitions for (free-standing) composite types

SELECT typ.oid, att.attname, att.atttypid

FROM pg_type AS typ

JOIN pg_namespace AS ns ON (ns.oid = typ.typnamespace)

JOIN pg_class AS cls ON (cls.oid = typ.typrelid)

JOIN pg_attribute AS att ON (att.attrelid = typ.typrelid)

WHERE

(typ.typtype = 'c' AND cls.relkind='c') AND

attnum > 0 AND -- Don't load system attributes

NOT attisdropped

ORDER BY typ.oid, att.attnum
2022-10-17 00:01:21.118 +07 [[unknown]][6340][apollo_portal] LOG: could not
send data to client: An established connection was aborted by the software
in your host machine.


2022-10-17 00:01:21.118 +07 [[unknown]][6340][apollo_portal] STATEMENT: --
Load field definitions for (free-standing) composite types

SELECT typ.oid, att.attname, att.atttypid

FROM pg_type AS typ

JOIN pg_namespace AS ns ON (ns.oid = typ.typnamespace)

JOIN pg_class AS cls ON (cls.oid = typ.typrelid)

JOIN pg_attribute AS att ON (att.attrelid = typ.typrelid)

WHERE

(typ.typtype = 'c' AND cls.relkind='c') AND

attnum > 0 AND -- Don't load system attributes

NOT attisdropped

ORDER BY typ.oid, att.attnum


From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: thien(dot)phan(at)apollo(dot)edu(dot)vn, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17645: Strange queries that stuck in database system
Date: 2022-10-17 08:15:16
Message-ID: 20221017081516.g2elezml2fppsubf@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 503 토토 사이트 페치 실패

Hi,

On Sun, Oct 16, 2022 at 11:43:24PM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17645
> Logged by: Thien, Phan Phuoc
> Email address: thien(dot)phan(at)apollo(dot)edu(dot)vn
> PostgreSQL version: 14.0

Unrelated, but you should definitely update to the latest minor version (so
14.5 right now).

> Operating system: Windows Server 2012 R2
> Description:
>
> When I run this query
>
> SELECT NOW() - query_start AS elapsed, pid, client_addr, query,
> query_start, *
> FROM pg_stat_activity
> WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%'
> ORDER BY query_start DESc;
>
> I noticed that there are many queries (as below) that create many Windows
> processes and CPU is 100%. Is it a bug? Please help!

Nothing here looks like a bug. Note that your query is incorrect as there's a
dedicated "state" field to give this information since version 9.2, so a bit
more than 10 years ago. You can refer to
/docs/14/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW
for more details about this view.

I'm not sure if you had question related to the rest of the message, but if you
do please send a message to pgsql-general list instead
(/list/)