Re: Autovacuum degrades all other operations by keeping all buffersdirty? - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Autovacuum degrades all other operations by keeping all buffersdirty?
Date
Msg-id 20180831223147.f6papgxo7bb3xajd@alvherre.pgsql
Whole thread Raw
In response to Autovacuum degrades all other operations by keeping all buffers dirty?  (David Pacheco <dap@joyent.com>)
Responses Re: Autovacuum degrades all other operations by keeping all buffersdirty?  (Andres Freund <andres@anarazel.de>)
List pgsql-general
On 2018-Aug-31, David Pacheco wrote:

> From reading the 9.6.3 source, it looks like the autovacuum process
> itself is single-threaded, and it reads pages essentially linearly
> from the relation (possibly skipping some).  When the autovacuum
> process needs to modify a page, it doesn't write it directly, but
> rather marks the buffer dirty.  The page will be written later,

Unless there's some bug, there is a BufferAccessStrategy that only lets
a few dozen buffers go unwritten before the autovac worker process
itself is forced to write some.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-general by date:

Previous
From: David Pacheco
Date:
Subject: Autovacuum degrades all other operations by keeping all buffers dirty?
Next
From: Andres Freund
Date:
Subject: Re: Autovacuum degrades all other operations by keeping all buffersdirty?