Re: Application EventLog: could not write to log file: Bad file descriptor

sorry, forgot to cc: to the group..To: Alvaro Herrera <
alvherre(at)commandprompt(dot)com>

not as far as I can tell... I have log_destination='stderr'. unless csv
logging is enabled in another location?

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:))

Thanks.
Ati

On Fri, Jun 6, 2008 at 11:24 PM, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
wrote:

> Ati Rosselet escribió:
> > Using postgresql 8.3 on windows 2003 server. I keep seeing this message
> in
> > my system log. Checking the times, it seems to coincide with a log
> > rollover each time, almost as though the db were trying to log something
> at
> > precisely the same time as it is closing access to the old file, and
> before
> > opening the new file.. and so fails to write.. does this make sense?
> has
> > anyone else seen this? Solutions? Ideas? I reduced logging, and
> disabled
> > the debugging plugin (still don't know how that got enabled.. I must have
> > missed something on the install). Hope that helps....
>
> Do you have CSV logging enabled?
>
> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> The PostgreSQL Company - Command Prompt, Inc.
>