On Thu, 6 May 1999, Bruce Momjian wrote:
> Date: Thu, 6 May 1999 01:20:13 -0400 (EDT)
> From: Bruce Momjian <maillist@candle.pha.pa.us>
> To: Taral <taral@taral.net>
> Cc: Tom Lane <tgl@sss.pgh.pa.us>, Oleg Bartunov <oleg@sai.msu.su>,
> hackers@postgreSQL.org
> Subject: Re: [HACKERS] posmaster failed under high load
>
> > 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.
>
How to explain that process with PID 701 which shown in ps output
as (postmaster) after some time becomes looks as usual postgres
Oleg
> --
> Bruce Momjian | http://www.op.net/~candle
> maillist@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
