| From: | Vick Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Vacuum process waiting on BufferPin |
| Date: | 2018-08-14 13:23:23 |
| Message-ID: | CALd+dceTTCsrfOh5BjLos3Rim+GTS0iCDiA0t9L-J-Uv+O-Bpg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Aug 14, 2018 at 9:21 AM, Don Seiler <don(at)seiler(dot)us> wrote:
> On Mon, Aug 13, 2018 at 5:55 PM, Vick Khera <vivek(at)khera(dot)org> wrote:
>
>> On Mon, Aug 13, 2018 at 5:19 PM, Don Seiler <don(at)seiler(dot)us> wrote:
>>
>>>
>>> I don't quite follow this. What circumstances would lead to this
>>> situation?
>>>
>>
>> BEGIN WORK;
>> DECLARE CURSOR ... ;
>> FETCH ...; -- for some number of fetches, which does not reach the end
>> of the cursor.
>>
>> then just sit there idle, without having closed the cursor or fetching
>> anything more.
>>
>
> So the fix in that case would be to ensure that they CLOSE the cursors
> when done with them?
>
>
The general fix is to never sit idle in transaction, but this specific case
closing the cursor seems like it will also do it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Seiler | 2018-08-14 13:26:03 | Re: Vacuum process waiting on BufferPin |
| Previous Message | Don Seiler | 2018-08-14 13:21:20 | Re: Vacuum process waiting on BufferPin |