On Mon, 16 Dec 2002, Justin Clift wrote:
> 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.
>
> [edited]
> 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.
>
I'm coming into this late, don't know what's been said before in this thread
and considering the above mention of dumping I'm probably completely off the
charts on the uselessness of this question/suggestion but...
Are you using a 'lazy' memory allocation setup. You could find that suddenly
finding the requested memory isn't really there when told it was when
requesting it has nasty effects.
I presume the normal talk of core dumps etc has happened.
--
Nigel Andrews