Re: BUG #16054: Slowest individual queries
| От | Jeff Janes |
|---|---|
| Тема | Re: BUG #16054: Slowest individual queries |
| Дата | |
| Msg-id | CAMkU=1w5PoaTJCJ15G7p+eSjQwrDb2ugEDvQXBHvEmF5J8Z84A@mail.gmail.com обсуждение исходный текст |
| Ответ на | BUG #16054: Slowest individual queries (PG Bug reporting form <noreply@postgresql.org>) |
| Список | pgsql-bugs |
On Sun, Oct 13, 2019 at 10:28 PM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:
Bug reference: 16054
Logged by: Gowri Sankar
Email address: a.gowri82@gmail.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;
Someone has declared a cursor, and is fetching from it. When I see these types of queries, they are usually coming from postgres_fdw.
It is annoying that it shows you the FETCH statement itself, and not the original statement. If you can use auto_explain, which will show you the original statement.
Cheers,
Jeff
В списке pgsql-bugs по дате отправления: