Well I can't get any better backtraces (even with --enable-debug). The strange thing is that this just happens once in a while and the process doesn't stop until it is killed (or postgre is restarted). Any suggestions ? Regards, Jernej Kos. On Sunday 12 of June 2005 18:01, you wrote: > Jernej Kos <kostko@xxxxxxxxxxxxxxxx> writes: > > Well there should be no complex queries executed (there are some huge > > tables, but the queries aren't huge or specially complicated). I tried > > attaching to the process via gdb and the process is executing method: > > > > HeapTupleSatisfiesSnapshot() > > > > The backtrace appears to be useless (too many ??s). Is that of any help ? > > It's really hard to see how it could get to HeapTupleSatisfiesSnapshot() > without being inside a query --- too bad you can't get a more usable > backtrace. Is it worth recompiling with --enable-debug to investigate > this? > > regards, tom lane -- Jernej Kos <kostko@xxxxxxxxxxxxxxxx> JWeb-Network ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend