| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Clemens Eisserer <linuxhippy(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #9161: wal_writer_delay is limited to 10s |
| Date: | 2014-02-15 09:27:18 |
| Message-ID: | 20140215092718.GE11943@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2014-02-15 09:59:25 +0100, Clemens Eisserer wrote:
> However, there is something to write - I perform a single insert
> operation every 10s.
>
> However this is just my pet project, and all I ask is why a parameter
> is artifically clipped ... it's not like I request some magical new
> feature.
Again. Changing that parameter to a higher value would change *nothing*,
because a commit *does* wake up the wal writer *independently* of the
parameter.
So it is a new feature you're requesting.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-02-15 16:52:44 | Re: BUG #8540: Avoid sscanf buffer overflow |
| Previous Message | Clemens Eisserer | 2014-02-15 08:59:25 | Re: BUG #9161: wal_writer_delay is limited to 10s |