On Thu, Oct 14, 2004 at 11:16:48AM +0200, Leonardo Francalanci wrote:
> I read "Chapter 23. Monitoring Database Activity" to monitor postgresql,
> but on Solaris it doesn't work. I tried "/usr/ucb/ps", but it doesn't
> work either (I only see the postmaster startup parameters). Isn't there
> any
"In addition, your original invocation of the postmaster command
must have a shorter ps status display than that provided by each
server process."
Yes, using PGDATA instead of the whole path eith the -D option worked:
now I can see the different status displays.
---(end of
On Thu, Oct 14, 2004 at 08:24:19AM -0600, Michael Fuhr wrote:
>
> As far as I can tell, for /usr/ucb/ps the show the replacement
> arguments, the sum of the lengths of the replacement arguments
> must be 2 or more greater than the sum of the lengths of the
> original arguments. I'm guessing that
On Thu, Oct 14, 2004 at 11:14:10AM +0100, Richard Huxton wrote:
> Leonardo Francalanci wrote:
> >I read "Chapter 23. Monitoring Database Activity" to monitor postgresql,
> >but on Solaris it doesn't work. I tried "/usr/ucb/ps", but it doesn't
> >work either (I only see the postmaster startup para
Leonardo Francalanci wrote:
I read "Chapter 23. Monitoring Database Activity" to monitor postgresql,
but on Solaris it doesn't work. I tried "/usr/ucb/ps", but it doesn't
work either (I only see the postmaster startup parameters). Isn't there
any other solution to see what postgresql instances a
I read "Chapter 23. Monitoring Database Activity" to monitor postgresql,
but on Solaris it doesn't work. I tried "/usr/ucb/ps", but it doesn't
work either (I only see the postmaster startup parameters). Isn't there
any other solution to see what postgresql instances are doing?
-
