Re: [HACKERS] posmaster failed under high load

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Taral <taral(at)taral(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] posmaster failed under high load
Date: 1999-05-06 05:20:13
Message-ID: 199905060520.BAA14883@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Wed, 5 May 1999, Tom Lane wrote:
>
> > Nope, that theory is all wet --- the backend definitely does
> > PS_SET_STATUS("idle") before it waits for a query. Something is
> > *really* peculiar here, since your backtrace shows that the backend
> > has reached the point of waiting for client input. It is not possible
> > to get there without having done PS_SET_STATUS. So why does the process
> > still show up as "(postmaster)" in ps? Something is flaky about your
> > system's support of ps status setting, I think.
>
> You never altered the task_struct, and so it's still 'postmaster' there.
> Note the W... the process is paged out, so the argv is not available!

Yes, I remember now. To do ps-args you need to read the process address
space. If it is paged out, ps does not bring in the pages just to read
the args. This is probably as expected. If someone wants to add a
linux-specific fix for this, I guess you could, though I am not sure it
is worth it.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-05-06 05:25:28 Re: [HACKERS] can't compile
Previous Message Oleg Bartunov 1999-05-06 03:53:16 Re: [HACKERS] posmaster failed under high load