From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <pgadmin(at)pse-consulting(dot)de>, <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Server status query problem |
Date: | 2005-11-27 19:19:10 |
Message-ID: | 004d01c5f387$7939e501$6a01a8c0@valehousing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
-----Original Message-----
From: "Andreas Pflug"<pgadmin(at)pse-consulting(dot)de>
Sent: 27/11/05 18:01:01
To: "Dave Page"<dpage(at)vale-housing(dot)co(dot)uk>
Cc: "pgadmin-hackers"<pgadmin-hackers(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2005-11-29 09:00:54 | SVN Commit by dpage: r4764 - branches/REL-1_4_0_PATCHES/pgadmin3/src/include/images |
Previous Message | Andreas Pflug | 2005-11-27 18:00:57 | Re: Server status query problem |