Andreas Pflug wrote:
>> That way a central server could hold all of the configuration info for
>> the company databases, and people can connect to that central server
>> which will provide all the needed info for connecting to other databases.
> IMHO, it's not worth the effort. pgAdmin3 isn't targeted at end users,
> but at admins and developers.
Sorry Andreas, I was thinking this would be for admins and developers,
not end users. :)
> For unix, you can simply copy .pgadmin3 in the home directory, for win32
> it's the KEY_CURRENT_USER\SOFTWARE\pgAdmin III registry branch.
Sure, but that's a pain if you move between unix and win32 a lot, and/or
have a bunch of admin's.
I'm thinking of functionality that'll make administration of PG better
in larger environments. Having a central repository makes a nice
"foundation point" for building further functionality onto.
For example, with a centalised repository we could have some kind of
(SNMP?) daemon that keeps the repository updated with the status of the
If pgAdmin could also hook into this kind of repository, it could
leverage off of the information there. Definitions of servers and
databases, database status info (i.e. SNMP daemon as mentioned), perhaps
replication status, and that kind of thing.
Do you see where I'm trying to go with this?
Regards and best wishes,
In response to
pgadmin-support by date
|Next:||From: Justin Clift||Date: 2004-08-17 08:49:33|
|Subject: Re: Storing configuration in a centralised database?|
|Previous:||From: Donald Fraser||Date: 2004-08-17 08:27:13|
|Subject: Re: load project problems with pgAdmin II|