> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin at pse-consulting.de] 
> Sent: 01 October 2005 00:08
> To: Dave Page
> Cc: pgadmin-hackers at postgresql.org; Slony Mailing List
> Subject: Re: [pgadmin-hackers] Ready for beta yet?
> 
> Dave Page wrote:
> > OK, we'll aim for Tuesday then.
> 
> Yup, I'll give you a 'go'.
> 
> Um, seeing that apparently nothing I posted in the last 4 weeks to 
> slony-general is fixed appropriately or finally discussed, 
> and we really 
> need to roll a beta quite soon, I'm afraid we'll have to fork 
> the slony 
> creation scripts.
> We already discussed to include the creation scripts into pgadmin 
> installations to make administrator's life easier, but apparently we 
> *must* do that to have pgadmin working on slony 1.1.

No, that is a very *bad* idea. The Slony team have told us that they
don't thing the proposed changes are appropriate, so all that will end
up happening is that any users running pgAdmin will get told to come and
see us for support, or stop running a non-standard version of Slony. I
do not want us to have to deal with any Slony support beyond our own
code in pgAdmin (not including the Win32 port of course, but that's a
whole other issue).

What exactly do we need the admin nodes for? I'm assuming that you're
setting up the maintenance DB for the server as the admin node so we can
easily find all sets on that server - is that right? Perhaps for older
versions (well 1.1) we need to just find sets as we connect to any
individual databases, and use your original plan for 1.2 in which we use
a separate table as Jan/Chris have suggested?

Also, what has Chris K-L done in phpPgAdmin? I thought he was going to
use the admin nodes idea as well, but perhaps not...

Regards, Dave