Re: Why is wal_writer_delay limited to 10s? - Mailing list pgsql-general

From Peter Geoghegan
Subject Re: Why is wal_writer_delay limited to 10s?
Date
Msg-id CAEYLb_WQ9B+wZZrJC4=erJqqmf=NHS+SMoOZfORL=mYK=MNBRQ@mail.gmail.com
Whole thread Raw
In response to Re: Why is wal_writer_delay limited to 10s?  (Clemens Eisserer <linuxhippy@gmail.com>)
Responses Re: Why is wal_writer_delay limited to 10s?  (Peter Geoghegan <peter.geoghegan86@gmail.com>)
Re: Why is wal_writer_delay limited to 10s?  (Clemens Eisserer <linuxhippy@gmail.com>)
List pgsql-general
On Sat, Feb 1, 2014 at 3:40 PM, Clemens Eisserer <linuxhippy@gmail.com> wrote:
> Something like wal_writer_delay=600s would be ideal, I can afford to
> loose a 10min of data, but can't afford to get a corrupted database
> after power loss.

What Postgres version? The WAL Writer will hibernate on Postgres 9.2+.
walwriter.c says:

/*
 * Number of do-nothing loops before lengthening the delay time, and the
 * multiplier to apply to WalWriterDelay when we do decide to hibernate.
 * (Perhaps these need to be configurable?)
 */
#define LOOPS_UNTIL_HIBERNATE        50
#define HIBERNATE_FACTOR            25


--
Regards,
Peter Geoghegan


pgsql-general by date:

Previous
From: Clemens Eisserer
Date:
Subject: Re: Why is wal_writer_delay limited to 10s?
Next
From: Peter Geoghegan
Date:
Subject: Re: Why is wal_writer_delay limited to 10s?