Re: Vacuum process waiting on BufferPin

From: Don Seiler <don(at)seiler(dot)us>
To: Vick Khera <vivek(at)khera(dot)org>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Vacuum process waiting on BufferPin
Date: 2018-08-14 13:26:03
Message-ID: CAHJZqBD0ecLukUSVcU=waP93Z9nnxVM2+f9SF9L0wnOVM0Xwpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Aug 14, 2018 at 8:23 AM, Vick Khera <vivek(at)khera(dot)org> wrote:
>
>
> The general fix is to never sit idle in transaction, but this specific
> case closing the cursor seems like it will also do it.
>

Of course. I've let development know that they need to sort out why it's
left that way. But if they're also NOT closing cursors, that seems like
another bad practice to correct.

Would commit/rollback automatically close cursors opened in that
transaction?

Don.

--
Don Seiler
www.seiler.us

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message pavan95 2018-08-14 13:38:27 Re: Copying data from a CSV file into a table dynamically
Previous Message Vick Khera 2018-08-14 13:23:23 Re: Vacuum process waiting on BufferPin