On Thu, 06 Apr 2006 08:18:34 -0400 Jan Wieck <[EMAIL PROTECTED]> wrote:
> Briefly stopping and forcibly disconnecting all clients (pgpool is very > handy for that) from both, the old and the new origin, usually makes > switchover a lot smoother and faster. OK I'll bear that in mind for tonight's attempt :) > Since obviously the MOVE SET happened on node 1 but wasn't able to > complete on node 2, you must have had some backend on node 2 that kept a > lock on one of the replicated tables, preventing the event to replicate. Looking at scrollbacks in the cold light of day revealed a telltale sign - there was still a vacuum process running that I'd started hours earlier and forgot about - only a vacuum analyse, but I'm sure it won't have helped matters! > Restarting the postmaster of node 2 or any client application accessing > node 2 should have been enough. Heh, at least I'm now the wiser for this - many thanks :) Am hoping tonight's run will be much smoother =) Cheers, Gavin. _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
