Re: BUG #16054: Slowest individual queries

On Sun, Oct 13, 2019 at 10:28 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> 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;
>

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