Hello Louis, If you disconnect a node, this node is in detached state, If you
need to sync the data between the nodes I recommend you a Point in Time
Recovery, for more information about it you can visit this site.
http://www.postgresql-es.org/node/313
Regards.
----- "louis fridkis" <[email protected]> escribió:
> In our production system, we are running pgpool 2.2.2. We have two postgres
> 8.3.3 instances, each on a different host. We have configured pgpool in
> replication mode. We need to shut down the secondary host so we can move it
> to a different physical location. We do not want to stop the application from
> connecting to pgpool during the time that the secondary is down, or
> afterwords. I have indicated that this is not possible, because, if a change
> is made to the primary postgres DB while the secondary is down, then, if we
> start the secondary and attach it, using pcp_attach_node, the two DBs will be
> out-of-sync. The only way to rectify the out-of-sync condition, then, would
> be to dump the primary and load it into the secondary. But, this also would
> not work, because, if any changes were made, to the primary DB, between the
> time the dump was made and the time it was loaded then the two DBs would
> still be out-of-sync. My question is: am I correct? Is there any way to avoid
> shutting down pgpool in this scenario?
>
Lou ...
>
>
> _______________________________________________ Pgpool-general mailing list
> [email protected]
> http://pgfoundry.org/mailman/listinfo/pgpool-general
_______________________________________________
Pgpool-general mailing list
[email protected]
http://pgfoundry.org/mailman/listinfo/pgpool-general
