On 12.03.2012 15:30, Fujii Masao wrote:
On Mon, Mar 12, 2012 at 10:27 PM, Fujii Masao wrote:
On Mon, Mar 12, 2012 at 7:58 PM, Heikki Linnakangas
wrote:
I also think we should backport commit
cff75130b5f63e45423c2ed90d6f2e84c21ef840, except for the removal of
wal_sender_delay).
Agreed. The
On Mon, Mar 12, 2012 at 10:27 PM, Fujii Masao wrote:
> On Mon, Mar 12, 2012 at 7:58 PM, Heikki Linnakangas
> wrote:
>> On 09.03.2012 13:40, Fujii Masao wrote:
>>>
>>> I found the bug which causes walsender to enter into busy loop
>>> when replication connection is terminated. Walsender consumes
>
On Mon, Mar 12, 2012 at 7:58 PM, Heikki Linnakangas
wrote:
> On 09.03.2012 13:40, Fujii Masao wrote:
>>
>> I found the bug which causes walsender to enter into busy loop
>> when replication connection is terminated. Walsender consumes
>> lots of CPU resource (%sys), and this situation lasts until
On 09.03.2012 13:40, Fujii Masao wrote:
I found the bug which causes walsender to enter into busy loop
when replication connection is terminated. Walsender consumes
lots of CPU resource (%sys), and this situation lasts until it has
detected the termination of replication connection and exited.
T
Hi,
I found the bug which causes walsender to enter into busy loop
when replication connection is terminated. Walsender consumes
lots of CPU resource (%sys), and this situation lasts until it has
detected the termination of replication connection and exited.
The cause of this bug is that the wals
