From: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, iliya g <gyozov2004(at)yahoo(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Postgres process |
Date: | 2011-08-09 16:38:04 |
Message-ID: | CA+h6Ahj9qU=gH-wW-9o+G4dGth8ke24PWL5aBS-uOXxxh3ZmYA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ahh,,, I missed this.. :)
Thank you Tom for pointing to appropriate direction. Below command worked
/usr/ucb/ps -ww <PID>
--Raghav
On Tue, Aug 9, 2011 at 9:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> writes:
> > Still, my guess we cannot get the process description on SunOS.
>
> I surely hope you're not still running SunOS. If you mean Solaris,
> note what the manual says at
> http://www.postgresql.org/docs/9.0/static/monitoring-ps.html
>
> Tip: Solaris requires special handling. You must use /usr/ucb/ps,
> rather than /bin/ps. You also must use two w flags, not just one. In
> addition, your original invocation of the postgres command must have
> a shorter ps status display than that provided by each server
> process. If you fail to do all three things, the ps output for each
> server process will be the original postgres command line.
>
> This advice is close to ten years old, but might well still apply to
> recent Solaris releases.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-08-09 16:52:00 | Re: Read-only postgres instance |
Previous Message | Jerry Sievers | 2011-08-09 15:55:39 | Re: Dump SQL DDL of all functions in DB |