From: | Colin Strickland <cms(at)sift(dot)co(dot)uk> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | RE: Universal admin frontend |
Date: | 2001-06-21 09:55:59 |
Message-ID: | 200106210955.f5L9txk06856@mongoose.office.sift.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 21 Jun 2001 19:23:09 +1000, Mark Pritchard wrote:
> > >PostgreSQL is written completely in C. The development community
> > >has shown that it is
> [snip]
> > >The administration task can be separated in 2 different tasks:
> [snip]
>
> Isn't this essentially the split between postmaster/workers and a client?
> i.e. I don't know how much value is added by introducing another
> communication protocol when JDBC would work fine. From my understanding of
> the users API you can handle pretty much everything other than pg_dump. Eg
> CREATE USER, CREATE DATABASE etc can all be issued from a client using
> standard PostgreSQL SQL.
>
> I'd have to cast my vote on the Java frontend.
>
> Cheers,
>
> Mark Pritchard
>
For an admin tool you might want to display OS info , server load,
database file sizes, logfile viewing etc.
I have been working on such a tool for my own use , ( GTK+ based front
end) and decided that a client / server model would be the most useful
approach. I was probably going to write a separate daemon rather than
integrate new stuff into the backend.
--
Colin M Strickland perl -e'print "\n",map{chr(ord()-3)}(reverse split
//,"\015%vhlwlqxpprF#ir#uhzrS#hkw#jqlvvhqudK%#\015\015nx".
"1rf1wilv1zzz22=swwk###369<#84<#:44#77.={di##339<#84<#:44#77.=ohw\015]".
"K9#4VE#/ORWVLUE#/whhuwV#dlurwflY#334#/wilV\015uhsrohyhG#ehZ#urlqhV");'
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2001-06-21 09:59:49 | Re: stuck spin lock with many concurrent users |
Previous Message | Mark Pritchard | 2001-06-21 09:23:09 | RE: Universal admin frontend |