Re: wal_sender_delay is still required? - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: wal_sender_delay is still required?
Date
Msg-id AANLkTikEk-Cqd3=L7A3eOWG7z2Te8N=tPdguXM__RCHM@mail.gmail.com
Whole thread Raw
In response to Re: wal_sender_delay is still required?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: wal_sender_delay is still required?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Dec 7, 2010 at 12:08 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Fujii Masao <masao.fujii@gmail.com> writes:
>> Walsender doesn't need the periodic wakeups anymore, thanks to
>> the latch feature. So wal_sender_delay is basically useless now.
>> How about dropping wal_sender_delay or increasing the default
>> value?
>
> If we don't need it, we should remove it.

The attached patch removes wal_sender_delay and uses hard-coded
10 seconds instead of wal_sender_delay as the delay between activity
rounds for walsender.

One problem with the patch is that it takes longer (at most 10s) to
detect the unexpected death of postmaster (by calling PostmasterIsAlive()).
This is OK for me. But does anyone want to specify the delay to detect
that within a short time?

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: profiling connection overhead
Next
From: Itagaki Takahiro
Date:
Subject: Re: Per-column collation