From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | a(dot)gowri82(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16054: Slowest individual queries |
Date: | 2019-10-14 11:24:21 |
Message-ID: | 20191014112421.k2n5bpvyguuibmgn@development |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Oct 14, 2019 at 02:24:10AM +0000, PG Bug reporting form wrote:
>The following bug has been logged on the website:
>
>Bug reference: 16054
>Logged by: Gowri Sankar
>Email address: a(dot)gowri82(at)gmail(dot)com
>PostgreSQL version: 10.9
>Operating system: Amazon Linux
>Description:
>
>Hi
>We can see from below similar queries are frequently reported as Slowest
>individual queries. During the same time period high Read IOPS .Please let
>me know what is the cause for this fetch statements. Let me know as well
>regards this more information.
>
>FETCH 100 FROM c2;
>FETCH 100 FROM c6;
>FETCH 100 FROM c2;
>
This is very clearly not a bug report, but a question about slow query.
And a woefully incomplete one, because we have no idea what the query
does, whether it's the cause or victim of high I/O usage, etc.
Please read https://wiki.postgresql.org/wiki/Slow_Query_Questions and
then post a question to either pgsql-general or pgsql-performance with
more detailed info.
regars
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2019-10-14 13:08:27 | BUG #16055: pgAdmin 4 - ERROR: operator does not exist: - oid |
Previous Message | PG Bug reporting form | 2019-10-14 02:24:10 | BUG #16054: Slowest individual queries |