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, 2008 at 5:11 PM, Alvaro Herrera <[EMAIL PROTECTED]> wrote: > 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 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. >
