On 12.03.2012 15:30, Fujii Masao wrote:
On Mon, Mar 12, 2012 at 10:27 PM, Fujii Masaomasao.fu...@gmail.com wrote:
On Mon, Mar 12, 2012 at 7:58 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
I also think we should backport commit
cff75130b5f63e45423c2ed90d6f2e84c21ef840,
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.
On Mon, Mar 12, 2012 at 7:58 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com 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
On Mon, Mar 12, 2012 at 10:27 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Mon, Mar 12, 2012 at 7:58 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 09.03.2012 13:40, Fujii Masao wrote:
I found the bug which causes walsender to enter into busy loop
when replication
