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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Ati Rosselet <ati(dot)rosselet(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Application EventLog: could not write to log file: Bad file descriptor
Date: 2008-06-09 15:11:47
Message-ID: 20080609151147.GC5026@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ati Rosselet escribió:
> 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?

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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2008-06-09 17:09:55 Re: fitler database list
Previous Message Andreas Kretschmer 2008-06-09 14:58:44 Re: "connect by"