| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | a(dot)gowri82(at)gmail(dot)com |
| Subject: | BUG #16054: Slowest individual queries |
| Date: | 2019-10-14 02:24:10 |
| Message-ID: | 16054-3b4039bbcf6d60b9@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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;
Regards,
Gowri.
PostgreSQL DBA.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-10-14 11:24:21 | Re: BUG #16054: Slowest individual queries |
| Previous Message | Tomas Vondra | 2019-10-13 20:38:48 | Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 |