On Wed, 28 Jan 2004, MaRCeLO PeReiRA wrote:
> Hi,
>
>
> > Is the machine becoming unresponsive? I.e. is it
> > taking several seconds
> > for things like ls to run?
>
> It isn't the case! I can do everything without
> problem, and without losing performance. The main
> problem is the postmaster daemon, that die. (really
> ;-)
>
> > What does top show for postgresql memory and cpu
> > usage?
>
> The top output is something like this:
>
> top - 16:44:24 up 2 days, 6:15, 10 users, load
> average: 1.24, 1.16, 1.05
> Tasks: 123 total, 4 running, 119 sleeping, 0
> stopped, 0 zombie
> Cpu(s): 96.0% user, 4.0% system, 0.0% nice,
> 0.0% idle
> Mem: 256292k total, 243696k used, 12596k free,
> 14024k buffers
> Swap: 530104k total, 82568k used, 447536k free,
> 114312k cached
>
> > Is postgresql really freezing, or just running
> > REALLY slow? I.e.
> > sometimes if you wait long enough you can get in to
> > what seems to be a
> > frozen database
>
> No way! It really die!! :(
>
Can you perhaps build it with debugging symbols and run it until it crashs
again and then send us the core file? You should check that the core file will
be generated first, by checking things like the ulimit for core files that the
postgresql server runs with.
--
Nigel Andrews