This is a discussion on Re: Server status query problem within the pgsql Interfaces Pgadmin Hackers forums, part of the PostgreSQL category; --> -----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 ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| -----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 ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |
| Thread Tools | |
| Display Modes | |
|
|