Re: How to cripple a postgres server

From: Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How to cripple a postgres server
Date: 2002-05-29 04:42:48
Message-ID: 1022647368.4690.31.camel@ws12
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2002-05-29 at 13:55, Tom Lane wrote:
> Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au> writes:
> > Not at all like the vacuum problem. Do you have any other tests I can
> > run? Other diagnostics that might help?
>
> This is a long shot, but ... does the behavior change if you remove the
> two lines
>
> if (signo != SIGALRM)
> act.sa_flags |= SA_RESTART;
>
> near the bottom of src/backend/libpq/pqsignal.c ? I am wondering if
> Linux gets unhappy if we try to do much in a signal handler. This
> looks to be the simplest alteration that might address such a problem.
>
> regards, tom lane

Maybe it does help. I've only seen the problem once now (just after
startup) rather than every few minutes... I'm still seeing lots of
processes in the ready queue every now and then, but they are doing more
sensible things.

I'll investigate some more and be more certain.

Stephen

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Fathi Ben Nasr 2002-05-29 08:40:04 creating tables with blob types
Previous Message Tom Lane 2002-05-29 03:55:57 Re: How to cripple a postgres server