Re: patch to allow disable of WAL recycling

From: Andres Freund <andres(at)anarazel(dot)de>
To: Jerry Jelinek <jerry(dot)jelinek(at)joyent(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: patch to allow disable of WAL recycling
Date: 2018-07-05 21:39:10
Message-ID: 20180705213910.lextkj7tv23rcxvb@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2018-06-26 07:35:57 -0600, Jerry Jelinek wrote:
> + <varlistentry id="guc-wal-recycle" xreflabel="wal_recycle">
> + <term><varname>wal_recycle</varname> (<type>boolean</type>)
> + <indexterm>
> + <primary><varname>wal_recycle</varname> configuration parameter</primary>
> + </indexterm>
> + </term>
> + <listitem>
> + <para>
> + When this parameter is <literal>on</literal>, past log file segments
> + in the <filename>pg_wal</filename> directory are recycled for future
> + use.
> + </para>
> +
> + <para>
> + Turning this parameter off causes past log files segments to be deleted
> + when no longer needed. This can improve performance by eliminating
> + read-modify-write operations on old files which are no longer in the
> + filesystem cache.
> + </para>
> + </listitem>
> + </varlistentry>

This is formulated *WAY* too positive. It'll have dramatic *NEGATIVE*
performance impact of non COW filesystems, and very likely even negative
impacts in a number of COWed scenarios (when there's enough memory to
keep all WAL files in memory).

I still think that fixing this another way would be preferrable. This'll
be too much of a magic knob that depends on the fs, hardware and
workload.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-07-05 21:41:28 Re: documentation fixes for partition pruning, round three
Previous Message Peter Eisentraut 2018-07-05 21:39:01 Re: make installcheck-world in a clean environment