On 3/21/2006 12:11 PM, Sven Willenberger wrote:
> We have a server acting mainly as a subscriber node for a handful of
> tables as well as having its own set of tables that are not involved in
> any replication scheme. The server itself is going to be replace by new
> hardware so it will not be needed. The question is will a pg_dump work
> in transferring the "metadata" regarding replication as well as the
> normal tables? The reason I ask this has to do with triggers and how
> they are attached to the oid of a primary key (or something like that)
> and how that affects pg_dump/restore. 

Your doubts are right, it will NOT work because of exactly those 
triggers that are "parked" out of the way. What you could do to migrate 
is the following:

1) Create a new SET that originates on the node you want to replace
    (old system).

2) Add those local tables currently not involved to that new set.

3) Put both schemas onto the new system and make it a new node.

4) Subscribe the new node to both sets and let catch up.

5) Do a switchover to transfer the new set to the new system.

6) Make sure the new system now subscribes the old set from the origin.

7) Stop the old subscriber and issue a DROP NODE for it.

8) If you don't intend to replicate those local tables, drop the new set
    to make them just local tables on the new server.


Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #