Re: How to cripple a postgres server

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

Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au> writes:
> I've already strace'ed the idle backend, and I can see the SIGUSR2 being
> delivered just before everything goes bad.

Yes, but what happens after that?

If you don't see anything obvious by examining a single process, maybe
strace'ing the postmaster + all descendant processes would offer a
better viewpoint.

> What resource would you think idle backends might be exhausting?

Difficult to say. I suspect your normal load doesn't have *all* the
backends trying to run queries at once. But in any case the SIGUSR2
event should only produce a momentary spike in load, AFAICS.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-05-28 14:02:18 Re: Invalid length of startup packet
Previous Message webmaster 2002-05-28 13:02:39 Database Rights