public inbox for [email protected]  

help / color / mirror / Atom feed

From: Laurenz Albe <[email protected]>
To: vinay kumar <[email protected]>
To: [email protected]
Subject: Re: Understanding recovery conflict due to bufferpin
Date: Wed, 17 Mar 2021 13:41:47 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMdzBEkg+EytT1XcsykcsarpLVu+oQcDV4ekdf6CMjOv8JpvyA@mail.gmail.com>
References: <CAMdzBEkg+EytT1XcsykcsarpLVu+oQcDV4ekdf6CMjOv8JpvyA@mail.gmail.com>

On Wed, 2021-03-17 at 10:14 +0530, vinay kumar wrote:
> Need some understanding regarding recovery conflict due to buffer pin. 
> 
> We see "User was holding shared buffer pin for too long" .
> 
> I understand that this can be due to holding lock to update content of a db block or page. 
> 
> 1> Is the lock held on a buffer page or page at disk level?

A buffer page.  And it is not a lock, it is a pin

> 2> Is there any serialization present to maintain the locking mechanism?

I don't quite understand - what you observe *is* the serialization
of access.

See this blog for some details:
https://www.cybertec-postgresql.com/en/streaming-replication-conflicts-in-postgresql/

Yours,
Laurenz Albe

view thread (5+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Understanding recovery conflict due to bufferpin
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox