Re: Proposed patch: Smooth replication during VACUUM FULL

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Gabriele Bartolini <gabriele(dot)bartolini(at)2ndquadrant(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposed patch: Smooth replication during VACUUM FULL
Date: 2011-05-02 06:44:39
Message-ID: BANLkTimAed=DbsJ6AMGWC35eYMfAhGOLvQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, May 1, 2011 at 9:31 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> I don't think the performance of replication is at issue. This is
> about resource control.
>

The unspoken question here is why would replication be affected by i/o
load anyways? It's reading data file buffers that have only recently
been written and should be in cache. I wonder if this system has
chosen O_DIRECT or something like that for writing out wal?

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-05-02 09:55:05 Re: Proposed patch: Smooth replication during VACUUM FULL
Previous Message Joseph Conway 2011-05-02 06:26:05 clog_redo causing very long recovery time