Re: How to cripple a postgres server - Mailing list pgsql-general

From Tom Lane
Subject Re: How to cripple a postgres server
Date
Msg-id 29597.1022553843@sss.pgh.pa.us
Whole thread Raw
In response to Re: How to cripple a postgres server  (Stephen Robert Norris <srn@commsecure.com.au>)
Responses Re: How to cripple a postgres server
List pgsql-general
Stephen Robert Norris <srn@commsecure.com.au> writes:
>> If you're seeing load peaks in excess of what would be observed with
>> 800 active queries, then I would agree there's something to investigate
>> here.

> Yep, indeed with 800 backends doing a query every second, nothing
> happens.

> The machine itself has 1GB of RAM, and uses no swap in the above
> situation. Instead, system time goes to 99% of CPU. The machine is a
> dual-CPU athlon 1900 (1.5GHz).

> It _only_ happens with idle connections!

Hmm, you mean if the 800 other connections are *not* idle, you can
do VACUUMs with impunity?  If so, I'd agree we got a bug ...

            regards, tom lane

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: is there any backend (server) timeout undocumented?
Next
From: Francisco Reyes
Date:
Subject: FreeBSD vs Red Hat. Will give feedback soon (Re: Moving data from FreeBSD to Red Hat)