Thanks Dave.
But I am having some trouble trying to get replication to work.
Here is what I did:
1) On master server:
a) I registered: lib/slevent.dll
b) I register as a service: slon -regservice
c) slon -listengines
2 engine(s) registered for service 'Slony-I'
Engine 1: E:\Program Files\PostgreSQL\8.2\data\slon.conf
Engine 2: E:\Program Files\PostgreSQL\8.2\data\master.conf
d) Started the slon service via manage->services
2) On Slave Server
a) I registered: lib/slevent.dll
b) I register as a service: slon -regservice
c) slon -listengines
2 engine(s) registered for service 'Slony-I'
Engine 1: E:\Program Files\PostgreSQL\8.2\data\slon.conf
Engine 2: E:\Program Files\PostgreSQL\8.2\data\slave.conf
d) Started the slon service via manage->services
3) Launched: pgAdmin3 (v1.6.2)
a) Created Master Server Connection
b) Selected database: MyTest
c) Right-clicked Replication object, selected from menu: New slony-I Cluster
...
d) Join existsing cluster: [unchecked]
Server: <Master-Server-Name> [Greyed out]
Database: MyTest [Entered data]
Cluster Name: <Master-HostName>-Master-Cluster [entered data]
Local Node: 1, Value: "Master Node" [entered data]
Admin Node: 99, Value: "pgAdmin Node" [entered data]
Comment: <empty> [no data entered]
d) Clicked OK and Completed structure shows:
<Master Hostname>-Master-Cluster
Nodes (2)
Master Node
Paths (0)
listens (0)
pgAdmin Node
Paths (1)
Master Node
listens (1)
Master Node (Master Node)
Replication Sets (0)
At this point, I tried to add a slave node but was unable to:
a) I tried (on Master server) connection:
1) Right-clicked Replication object, selected from menu: New slony-I
Cluster ...
2) Join existing cluster: [checked]
Server: Master-Server-Name [no change]
Database: MyTest [no change]
Cluster-name: <Master-Server-Name>
Local Node: 2, Value: "Slave Node" [entered data]
Admin node: "99 - pgAdmin Node" [no change]
Comment: <empty> [no data entered]
3) Clicked OK and...
"An error has occurred:
ERROR: schema "_<Master-Host-Server>-Master-Cluster" already exists
"
So, perhaps I should not have added a join here, in the master server
connection,
so I clicked CANCEL
b) Then I tried (on Slave Server) connection:
1) Right-clicked Replication object, selected from menu: New slony-I
Cluster ...
2) Join existing cluster: [checked]
Server: <Slave-Server-Name> [Initially was Greyed out, but active
after a delay]
Database: MyTest [unchanged]
Cluster Name: <empty> [dropdown shows empty list and not selecteable]
Local Node: <empty>, Value: <empty>
Admin Node: <empty>, Value: <empty>
Comment: <empty>
At this point, it makes no sense to enter any fields after 'Cluster Name'
since
the 'Cluster Name' must have a value and 'OK' remains greyed out.
So I am at loss to go any further...
Any advice?
>-----Original Message-----
>From: Dave Page [mailto:[EMAIL PROTECTED]
>Sent: Monday, September 17, 2007 8:58 AM
>To: Daniel B. Thurman
>Cc: Pgadmin-Support (E-mail)
>Subject: Re: [pgadmin-support] Implementing Replication via pgAdmin
>
>
>Daniel B. Thurman wrote:
>> I have tried to follow the pgAdmin slony support in the help sections
>> of pgAdmin and it seems to be inconsistent. For example, it is not
>> intuitively clear from the help sections how exactly to
>setup the master
>> and slave configurations. From a windows client
>perspective, it seems
>> that one must use command-line operations in order to setup the slony
>> services, create and configure the configuration files, and
>then try to use
>> the pgAdmin replication objects to define the master/slave
>relationships?
>
>Yes.
>
>> Since it is possible to create new connections to all of the
>postgreSQL
>> servers within your network into the pgAdmin connections
>list, should it
>> also be possible to seamlessly perform (slony) replication
>for all of the
>> master/slaves databases with slony services automatically
>initialized and
>> completely within pgAdmin without having to resort to manual
>command-line
>> operations?
>
>The slon daemon (on *nix) or service & engines (on Windows) must be
>configured from the command line. pgAdmin makes no attempt to do this
>because that is entirely OS dependent (in fact, it is distribution
>dependent because, for example, Redhat and Slackware start daemons in
>entirely different ways). In addition, you may not even want
>to run slon
>on the machine that you're running pgAdmin on, or even that you're
>running the database on.
>
>So yes, configure the slons on the command line, then use pgAdmin to
>create your replication clusters and sets.
>
>Regards, Dave
>
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.5.487 / Virus Database: 269.13.21/1012 - Release
>Date: 9/16/2007 6:32 PM
>
>
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.487 / Virus Database: 269.13.21/1012 - Release Date: 9/16/2007
6:32 PM
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
