Rafael Martinez wrote:
> CPU 50% idle, rest mainly used in "system". Virtually no IO. No
> blocked processes. An impressive amount of context switches. No swap.
>
> An strace(1) of the postgres process may give a hint about the "system"
> part; this is what it does over and over and over agai
Tom Lane wrote:
> Rafael Martinez <[EMAIL PROTECTED]> writes:
>
>> Any ideas why it is taking 2462558.813 ms to finish when the total time
>> for the deletion is 2.546 ms + 3.422 ms + 0.603ms?
>
Hei Tom, I got this information from my colleague:
> Is the problem repeatable?
Repeatable as in
Rafael Martinez <[EMAIL PROTECTED]> writes:
> manage=# EXPLAIN ANALYZE DELETE FROM module WHERE deviceid='7298';
> QUERY PLAN
> -
> Nested Loop (cost=0.00..14.63 rows=1 width=67) (actual
> time=2.365..
Hello
---
Postgresql version: 8.1.10
4GB RAM
2x HP 72GB 10K SAS RAID1/smartarray
---
I have a colleague that is having som performance problems from time to
time when deleting some rows from a table.
We found out that the database having this probl
