Re: again... (win32 logging errors) - Mailing list pgsql-general

From Klint Gore
Subject Re: again... (win32 logging errors)
Date
Msg-id 49052358.8070902@une.edu.au
Whole thread Raw
In response to again...  ("Ati Rosselet" <ati.rosselet@gmail.com>)
Responses Re: again... (win32 logging errors)  (Martin Gainty <mgainty@hotmail.com>)
List pgsql-general
Ati Rosselet wrote:
> I'm still getting a lot of these entries in my eventlog whenever I
> have a reasonably large amount of logging:
>
> Event Type:    Error
> Event Source:    PostgreSQL
> Event Category:    None
> Event ID:    0
> Date:        10/22/2008
> Time:        9:36:28 AM
> User:        N/A
> Computer:    ----------
> Description:
> could not write to log file: Bad file descriptor
>
> production server 8.3.3 (tried with 8.3.4 - same thing), win 2003
> server.  I'd send this to psql-bugs, but I can't figure out how to
> reproduce it.. and
> apparently noone else has seen this?   Or is noone else running
> postgres on win2003??? (survey says??)
>
> The timing of each appears to be when log is rolled over (size limited
> to 10MB) and postgres attempts to write a log entry at the same time:
>
> Any ideas? help? How to proceed???

Change the log settings to panic and up the size limit.  Almost nothing
gets written to the log and the log never gets full enough to rotate.
Other than that, you'll need to get visual studio and the source and
work it out.

Reproducing it is relatively easy - make a function that does raise
notice and call it a lot.  I had one that essentially took out the server.
http://archives.postgresql.org/pgsql-general/2008-08/msg00615.php

+1 for survey.

klint.

--
Klint Gore
Database Manager
Sheep CRC
A.G.B.U.
University of New England
Armidale NSW 2350

Ph: 02 6773 3789
Fax: 02 6773 3266
EMail: kgore4@une.edu.au


pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: Are there plans to add data compression feature to postgresql?
Next
From: Martin Gainty
Date:
Subject: Re: again... (win32 logging errors)