Re: [HACKERS] PinBuffer() no longer makes use of strategy - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] PinBuffer() no longer makes use of strategy
Date
Msg-id CANP8+jLzRoL4rRvj918MhK28DjD7b7symaQs6dtYVvZkHN23Vg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] PinBuffer() no longer makes use of strategy  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 4 February 2017 at 09:33, Andres Freund <andres@anarazel.de> wrote:

> For pretty much else that logic seems worse,
> because it essentially prevents any buffers ever staying in s_b when
> only ringbuffer accesses are performed.

That was exactly its intent. The ringbuffer was designed to avoid
cache spoiling by large scans.

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



pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: [HACKERS] ANALYZE command progress checker
Next
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Logical decoding on standby