From: | Erik Brandsberg <erik(at)heimdalldata(dot)com> |
---|---|
To: | Bindra Bambharoliya <bindra(dot)bambharoliya(at)gmail(dot)com> |
Cc: | pgsql-sql(at)lists(dot)postgresql(dot)org |
Subject: | Re: Cursor with hold for select takes too long |
Date: | 2024-03-22 17:39:39 |
Message-ID: | CAFcck8HEJa8-53SNWxMd_8D732skiihM4S7YEsEW63swywFosg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
What is the actual query being done, and how many rows are being returned?
Depending on the query, it could change the execution path, so this is
critical to understand. If you are doing an order by on a large
result-set, it may be doing a huge amount of processing to get your first
100 rows.
On Fri, Mar 22, 2024 at 12:50 PM Bindra Bambharoliya <
bindra(dot)bambharoliya(at)gmail(dot)com> wrote:
> Hi team,
> I am facing issues with cursor with hold for select.
>
> If I execute select quaery without cursor it takes 13 seconds,
> If execute it like
> Begin;
> Cursor "sql1" with hold for select.... ;fetch 100 to "sql1"
> It takes more than 3 minutes.
> Even sometimes it takes more than 10 minutes.
>
> What could be the problem?
> Request to help on this ASAP.
> I am facing this issue on production.
> I checked locks etc. But nothing like that.
>
>
> Thanks & Regards
> Bindra
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bindra Bambharoliya | 2024-03-22 17:47:11 | Re: Cursor with hold for select takes too long |
Previous Message | Bindra Bambharoliya | 2024-03-22 16:50:04 | Cursor with hold for select takes too long |