From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: linuxhippy@gmail.com
Subject: BUG #18474: wal_writer_delay limited to arbitrary value of 10s
Date: Wed, 22 May 2024 18:11:31 +0000
Message-ID: <18474-e2f89fa17c6ae72e@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18474
Logged by: Clemens Eisserer
Email address: linuxhippy@gmail.com
PostgreSQL version: 16.3
Operating system: Linux
Description:
wal_writer_delay has a hard-coded limit of 10000ms, however the limit seems
artificial because depending on the type of workload 10s are either very
long of very short.
As far as I know wal_writer_delay is the only option for scanrios where the
durability of recently commited data is not that important, yet
database-corruption - as it can happen with fsync=off - should be avoided.
E.g. I have postgresql running on a raspberry pi storing sensor data, and
every 250ms an additional row with sensor data is written. Because of
fsync=on I have huge amounts of write-amplification (gigabytes), and it
would be great if it batching e.g. 10min of sensor-data would be possible.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, linuxhippy@gmail.com
Subject: Re: BUG #18474: wal_writer_delay limited to arbitrary value of 10s
In-Reply-To: <18474-e2f89fa17c6ae72e@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox