Sorry, I don't think I made myself clear.  I don't want to query the DB
every few seconds to get its current status.  I want to keep an open an
open connection and have immediate access to all information like I have
when I set the debug level high and see everything going on inside the
DB right on my machine.

I guess think of it as a dashboard that constantly displays the db
status.  Something like 'top' rather than 'ps -ef|grep .....'.

As far as I understand, JDBC is just a mechanism to connect to a db,
execute queries, etc., not get this kind of info.

Shahbaz C.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Bruce Momjian
Sent: Thursday, February 13, 2003 7:18 PM
To: Shahbaz Chaudhary
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] java access to the backend (non jdbc)?


Well, we have jdbc at jdbc.postgresql.org.

------------------------------------------------------------------------
---

Shahbaz Chaudhary wrote:
> Hi All,
> I was wondering if there is a libq or libqxx type library written in
> java.  Even if it is done through jni.  I would like to do some
> experiments, perhaps make a utility that reads server information such
> as currently executing query, current locks, amount of disk/ram taken
up
> by pgsql.  Basically some very useful information for admins.  I've
> forgotten most of C, C++ (from college days), but would love to try my
> hand at such a utility...I'm sure there are others who would like to
use
> java to access such a backend.  Any pointers?
> 
> Shahbaz C.
> 
> 
> ---------------------------(end of
broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania
19073

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Reply via email to