Re: Application EventLog: could not write to log file: Bad file descriptor - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Application EventLog: could not write to log file: Bad file descriptor
Date
Msg-id 20080609151147.GC5026@alvh.no-ip.org
Whole thread Raw
In response to Re: Application EventLog: could not write to log file: Bad file descriptor  ("Ati Rosselet" <ati.rosselet@gmail.com>)
Responses Re: Application EventLog: could not write to log file: Bad file descriptor  ("Ati Rosselet" <ati.rosselet@gmail.com>)
Re: Application EventLog: could not write to log file: Bad file descriptor  ("Ati Rosselet" <ati.rosselet@gmail.com>)
List pgsql-general
Ati Rosselet escribió:
> sorry, forgot to cc: to the group..To: Alvaro Herrera <
> alvherre@commandprompt.com>
>
>
> not as far as I can tell... I have log_destination='stderr'.  unless csv
> logging is enabled in another location?

No, that should mean it's disabled.

> Since I disabled the following line:
>     shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'
> and changed logging from 'all' to 'mod'
> I have not seen the error, although that may just be because the amount
> logged is reduced drastically
> (from verbose due to logging all selects - to pretty much zero for normal
> website usage - very few modifying  queries:))

Yes, the problem is probably not gone but just made rarer.  ISTM it
would be good to debug it.  The Windows logger code does use two threads
for the logging (as opposed to everywhere else which uses a single
process) so it's quite possible that the locking is bogus somewhere.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-general by date:

Previous
From: Andreas Kretschmer
Date:
Subject: Re: "connect by"
Next
From: Craig Ringer
Date:
Subject: Re: fitler database list