Re: Application EventLog: could not write to log file: Bad file descriptor
| От | Ati Rosselet |
|---|---|
| Тема | Re: Application EventLog: could not write to log file: Bad file descriptor |
| Дата | |
| Msg-id | ce6402fc0806081540m4dd93401qae6c853f428320d5@mail.gmail.com обсуждение исходный текст |
| Ответ на | 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
|
| Список | pgsql-general |
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?
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
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@commandprompt.com> wrote:
Ati Rosselet escribió:Do you have CSV logging enabled?> 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....
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
В списке pgsql-general по дате отправления: