CentOS 6.0 - 2.6.32-220.13.1.el6.x86_64
PostgreSQL version: 8.4.11
Primarily checked on PG 8.4.9 (same OS), problem also occurs. Few times a
day I get a situation where PostgreSQL stops running for 1-2 minutes. CPU is
running 99% in systime. IO is OK, only interrupts are extremely high (over
100k
On Thu, Mar 1, 2012 at 1:52 PM, Paul Dunkler wrote:
>
> Hi,
>
> You're running on a box larger than I'm used to, so this is only speculation.
> I'm wondering whether you're hitting problems with lock contention or some
> such. It looks like you've got 48 cores there all at about 100% possibly no
Hi,You're running on a box larger than I'm used to, so this is only speculation. I'm wondering whether you're hitting problems with lock contention or some such. It looks like you've got 48 cores there all at about 100% possibly none of them getting much chance to do any work.Yes. That is what i se
On 01/03/12 19:41, Paul Dunkler wrote:
I did that now - and analyzed the situation a bit. There are only queries
running which will process very fast under high load (only index scans, very low
rates of sequential scans). I found a remarkable number of Insert statements...
And sometimes when tha
I did that now - and analyzed the situation a bit. There are only queries running which will process very fast under high load (only index scans, very low rates of sequential scans). I found a remarkable number of Insert statements...And sometimes when that happens, the CPU Utilization is going up
On 01/03/12 16:41, Paul Dunkler wrote:
Hi List,
we are currently running a rather large postgresql-installation with
approximately 4k Transactions and 50k index scans per second.
In the last days on some times of the day (irregular - 3-4 times a day), some
of the postmaster processes are runn
Hi List,
we are currently running a rather large postgresql-installation with
approximately 4k Transactions and 50k index scans per second.
In the last days on some times of the day (irregular - 3-4 times a day), some
of the postmaster processes are running with 100% cpu usage. That leads to a
