| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Drazen Kacar <drazen(dot)kacar(at)oradian(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Query cancellation on hot standby because of buffer pins |
| Date: | 2015-02-23 10:12:28 |
| Message-ID: | CA+U5nM+Gs7c3yi+sVwiiDWfXvQSwv=1NEMO2kpR5hUJ5cr_qwg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 23 February 2015 at 08:19, Drazen Kacar <drazen(dot)kacar(at)oradian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Drazen Kacar | 2015-02-23 10:35:48 | Re: Query cancellation on hot standby because of buffer pins |
| Previous Message | Drazen Kacar | 2015-02-23 08:19:59 | Re: Query cancellation on hot standby because of buffer pins |