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
Well.. I guess I'll just have to hope it pops up rarely enough to not be a
problem since I really don't have the capacity to try to debug postgres code
for the foreseeable future :) Should I log a bugreport, or a suspected bug
report (if such an animal exists...)? :)
Cheers
Ati
On Mon, Jun 9, 2
Ati Rosselet escribió:
> sorry, forgot to cc: to the group..To: Alvaro Herrera <
> [EMAIL PROTECTED]>
>
>
> 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 lin
sorry, forgot to cc: to the group..To: Alvaro Herrera <
[EMAIL PROTECTED]>
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'
an
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
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
op
