Re: pgsql: Update docs as to when WAL logging can be skipped.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Robert Haas <rhaas(at)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Update docs as to when WAL logging can be skipped.
Date: 2010-04-20 00:29:35
Message-ID: m2w603c8f071004191729wd848226aqe8061a8ccf772a6f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, Apr 19, 2010 at 8:26 PM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> Log Message:
> -----------
> Update docs as to when WAL logging can be skipped.
>
> In 8.4 and prior, WAL-logging could potentially be skipped whenever
> archive_mode=off.  With streaming replication, this is now true only
> if max_wal_senders=0.
>
> Fujii Masao, with light copyediting by me

Eh. I should have written "if it is also the case that max_wal_senders=0".

For the archives, here is the link to the original patch:

http://archives.postgresql.org/pgsql-docs/2010-03/msg00021.php

...Robert

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-04-20 01:38:52 pgsql: Move the responsibility for calling StartupXLOG into
Previous Message Robert Haas 2010-04-20 00:26:06 pgsql: Update docs as to when WAL logging can be skipped.