Re: [BUGS] log : bad file dscriptor???? - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: [BUGS] log : bad file dscriptor????
Date
Msg-id 65937bea1003111640q28c3a048yc0e004668f6c93cb@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] log : bad file dscriptor????  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: [BUGS] log : bad file dscriptor????
List pgsql-hackers
On Wed, Mar 18, 2009 at 3:47 AM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
Gurjeet Singh wrote:
   On Windows, the write to log file is done by a thread (whose main
function is pipeThread() ), and since it works completely independent of the
SysLoggerMain() ( which is responsible for calling logfile_rotate()
periodically, which in turn changes the global variable syslogFile) this is
causing a race condition due to an error in the way we are using the related
critical section.

Thanks, committed. I hope this helps with Ati's problems.


It seems this commit never made it to the release notes. A customer came asking for the fix to this very problem, and although we know that the issue has been fixed, we could not refer him to the release notes. All we could suggest was to do the minor upgrade.

I could not find any more reports of this bug after the fix was committed. So what would it take to make release notes say that it has been fixed?

Best regards,
--
gurjeet.singh
@ EnterpriseDB - The Enterprise Postgres Company
http://www.enterprisedb.com

singh.gurjeet@{ gmail | yahoo }.com
Twitter/Skype: singh_gurjeet

Mail sent from my BlackLaptop device

pgsql-hackers by date:

Previous
From: KaiGai Kohei
Date:
Subject: Re: renameatt() can rename attribute of index, sequence, ...
Next
From: Bruce Momjian
Date:
Subject: Re: Warning about invalid .pgpass passwords