Henrik Steffen wrote:
> hi tom,
>
> ok, I understand this.
>
> But: There is ONLY postgres running on this particular
> machine. And it's mostly when backup (dumpall) and/or
> vacuuming/reindexing is going on.
>
> In my opinion, postgresql does something on my machine
> that leads to these complete system lockups.
It sounds like the system lockups are occuring perhaps due to disk I/O, with PostgreSQL being the program causing the
disk load past what the system handles.
How much load does this system normally have, when there aren't dumps/vacuums/reindexes going on? Trying to understand
how much load your system normally copes with before locking up.
?
As a thought, if this is really being caused by disk I/O loads, then it might be able to trigger it on demand with disk
benchmarking programs (just an idle thought). That could be useful to know about.
Regards and best wishes,
Justin Clift
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi