Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



yup.. still there.. just reduced frequency... just got the first one since reducing the logging...  darn.. :(
I checked the fixes for the new release, but no mention of it. Does this mean no-one else has run into this? Or am I the only idiot running postgres on windows? :))
Cheers
Ati

On Mon, Jun 9, 2008 at 5:11 PM, Alvaro Herrera <alvherre@xxxxxxxxxxxxxxxxx> wrote:
Ati Rosselet escribió:
> sorry, forgot to cc: to the group..To: Alvaro Herrera <
> alvherre@xxxxxxxxxxxxxxxxx>
>
>
> 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.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux