Re: Query cancellation on hot standby because of buffer pins - Mailing list pgsql-admin

From Simon Riggs
Subject Re: Query cancellation on hot standby because of buffer pins
Date
Msg-id CA+U5nM+Gs7c3yi+sVwiiDWfXvQSwv=1NEMO2kpR5hUJ5cr_qwg@mail.gmail.com
Whole thread Raw
In response to Re: Query cancellation on hot standby because of buffer pins  (Drazen Kacar <drazen.kacar@oradian.com>)
Responses Re: Query cancellation on hot standby because of buffer pins  (Drazen Kacar <drazen.kacar@oradian.com>)
List pgsql-admin
On 23 February 2015 at 08:19, Drazen Kacar <drazen.kacar@oradian.com> wrote:

> At the time they happened on the standby there was vacuuming of one
> table participating in the select query on the primary.

The VACUUM will have generated a WAL record that needs super exclusive
access to the block. Since feedback was enabled that record would not
have removed data visible by the query, but still needs to edit the
block.

The query was pinning that block, so this situation led to a delay on
the standby, which then led to cancellation of the query.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services


pgsql-admin by date:

Previous
From: Drazen Kacar
Date:
Subject: Re: Query cancellation on hot standby because of buffer pins
Next
From: Drazen Kacar
Date:
Subject: Re: Query cancellation on hot standby because of buffer pins