Re: monitoring database activity on solaris

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David Parker" <dparker(at)tazznetworks(dot)com>
Cc: "postgres general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: monitoring database activity on solaris
Date: 2005-04-06 22:18:22
Message-ID: 6397.1112825902@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"David Parker" <dparker(at)tazznetworks(dot)com> writes:
> According to the 7.4 doc section on monitoring database activity, one
> should be able to see the current activity happening in a given postgres
> process. It mentions that on Solaris (which we are running on) you need
> to use /usr/ucb/ps, and it also says
>
> " your original invocation of the postmaster command must have a shorter
> ps status display than that provided by each server process "

Yeah. This is a Solaris peculiarity that we only figured out by chance.
The best bet is to make sure that your postmaster start script invokes
the postmaster as
postmaster
no more. No path (set PATH beforehand instead). No command-line
switches (whatever you might want there can be put into postgresql.conf
instead). Redirection is OK, but keep the command line itself to a
minimum. "postmaster" and nothing else will be shorter than any of the
ps display settings the postmaster's children use ... but if you have a
bunch of command-line arguments, it'll be longer, and Solaris' ps will
choose to display the wrong thing.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-04-06 22:22:02 Re: COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion
Previous Message Martijn van Oosterhout 2005-04-06 22:15:10 Re: Big trouble with memory !!