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 K
Jernej Kos <[EMAIL PROTECTED]> 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 bac
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
Jernej Kos <[EMAIL PROTECTED]> writes:
> i am using postgresql version 8.0.1 on Gentoo Linux and from time to time a
> postgres process that is marked as idle - "postgres: user db IP(34079) idle"
> - starts using 100% CPU. There is nothing in the logs, so i don't have a clue
> what could be the p
