Re: Application EventLog: could not write to log file: Bad file descriptor
От | Alvaro Herrera |
---|---|
Тема | Re: Application EventLog: could not write to log file: Bad file descriptor |
Дата | |
Msg-id | 20080609151147.GC5026@alvh.no-ip.org обсуждение исходный текст |
Ответ на | 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
Re: Application EventLog: could not write to log file: Bad file descriptor |
Список | 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 по дате отправления: