<div dir="ltr"><div class="gmail_quote">On Tue, Jun 1, 2010 at 11:02 AM, Jan Wieck <span dir="ltr"><<a href="mailto:JanWieck@yahoo.com" target="_blank">JanWieck@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div>On 6/1/2010 9:31 AM, Steve Singer wrote:<br>
> Jan Wieck wrote:<br>
>> On 5/28/2010 6:57 PM, Steve Singer wrote:<br>
><br>
>>><br>
>>> (A version of 2.0.4 RC1 + these changes can be found at<br>
>>> <a href="http://github.com/ssinger/slony/tree/203_memfixes_UlrichWeber" target="_blank">http://github.com/ssinger/slony/tree/203_memfixes_UlrichWeber</a>)<br>
>><br>
>> Is that the memory leak from not freeing notifications? If so, let's<br>
>> test it with bombarding a slon with a gazillion notifies and if it<br>
>> survives, put it into 2.0.4.<br>
>><br>
>><br>
><br>
> The patch frees memory in a number of places including the cleanup<br>
> thread and during the set copy. You can view the patch at the above URL.<br>
><br>
> The 1.2 version of the patch also removed the notify stuff (but that<br>
> wasn't required with 2.0 the code was removed). If we are happy with<br>
> things we should apply it to 1.2 as well for the next time we do a 1.2.x<br>
> release.<br>
<br>
</div></div>After a detailed line by line review of the patch, Steve and I decided<br>
to commit it for 2.0.4.<br>
<div><br></div></blockquote></div><br>Thank you :)<br><br>-- <br>gurjeet.singh<br>@ EnterpriseDB - The Enterprise Postgres Company<br><a href="http://www.EnterpriseDB.com" target="_blank">http://www.EnterpriseDB.com</a><br>
<br>singh.gurjeet@{ gmail | yahoo }.com<br>
Twitter/Skype: singh_gurjeet<br><br>Mail sent from my BlackLaptop device<br>
</div>