Tom Lane wrote:
David Parker [EMAIL PROTECTED] writes:
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
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
David Parker [EMAIL PROTECTED] 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
OK, thanks. We're using pg_ctl to start it at the moment, but we can
obviously change that.
- DAP
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 06, 2005 6:18 PM
To: David Parker
Cc: postgres general
Subject: Re: [GENERAL] monitoring database
David Parker [EMAIL PROTECTED] writes:
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
