Re: How to cripple a postgres server
| От | Tom Lane |
|---|---|
| Тема | Re: How to cripple a postgres server |
| Дата | |
| Msg-id | 29597.1022553843@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: How to cripple a postgres server (Stephen Robert Norris <srn@commsecure.com.au>) |
| Ответы |
Re: How to cripple a postgres server
|
| Список | 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 по дате отправления: