Re: Server status query problem - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Server status query problem
Date
Msg-id 004d01c5f387$7939e501$6a01a8c0@valehousing.co.uk
Whole thread Raw
In response to Server status query problem  (Dave Page <dpage@vale-housing.co.uk>)
List pgadmin-hackers

-----Original Message-----
From: "Andreas Pflug"<pgadmin@pse-consulting.de>
Sent: 27/11/05 18:01:01
To: "Dave Page"<dpage@vale-housing.co.uk>
Cc: "pgadmin-hackers"<pgadmin-hackers@postgresql.org>
Subject: Re: Server status query problem

> Arg....
> Testing for HOURS, coding it but you already committed it...

Sorry, I left it almost a week first - and figured you just had no objections.

/D

-----Unmodified Original Message-----
Dave Page wrote:
> Hi Andreas,
>
> It was pointed out to me that the server status lock tab doesn't show data
> correctly - specifically, the username is always blank, and the query string
> normally shows up as <backend information unavailable>.
>
> It seems the cause is that most of the stats functions don't take a PID as
> an argument, but a backend ID between 1 and the current number of backends.
>
> A hacked together replacement query looks like the following, but before I
> appy it I just wanted to run it past you and the list in case I missed
> anything:

Arg....
Testing for HOURS, coding it but you already committed it...


Regards,
Andreas

pgadmin-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: Server status query problem
Next
From: svn@pgadmin.org
Date:
Subject: SVN Commit by dpage: r4764 - branches/REL-1_4_0_PATCHES/pgadmin3/src/include/images