<div dir="ltr"><div class="gmail_quote">On Wed, Mar 18, 2009 at 3:47 AM, Heikki Linnakangas <span dir="ltr"><<a
href="mailto:heikki.linnakangas@enterprisedb.com">heikki.linnakangas@enterprisedb.com</a>></span>wrote:<br
/><blockquoteclass="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left:1ex;"><div class="im">Gurjeet Singh wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex;border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> On Windows, the write to log file is done by a
thread(whose main<br /> function is pipeThread() ), and since it works completely independent of the<br />
SysLoggerMain()( which is responsible for calling logfile_rotate()<br /> periodically, which in turn changes the global
variablesyslogFile) this is<br /> causing a race condition due to an error in the way we are using the related<br />
criticalsection.<br /></blockquote><br /></div> Thanks, committed. I hope this helps with Ati's problems.<br /><br
/></blockquote></div><br/>It seems this commit never made it to the release notes. A customer came asking for the fix
tothis very problem, and although we know that the issue has been fixed, we could not refer him to the release notes.
Allwe could suggest was to do the minor upgrade.<br /><br />I could not find any more reports of this bug after the fix
wascommitted. So what would it take to make release notes say that it has been fixed?<br clear="all" /><br />Best
regards,<br/>-- <br />gurjeet.singh<br />@ EnterpriseDB - The Enterprise Postgres Company<br /><a
href="http://www.enterprisedb.com">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>