On Sat, Apr 5, 2008 at 2:30 AM, Henry <henry at zen.co.za> wrote:
> On Fri, April 4, 2008 2:32 pm, Henry wrote:
>  > They're repeatedly restarting and copying the same tables - and never
>  > completing.
>
>  To clarify, "never completing" is probably not accurate; it's just been
>  repeating the truncate/copy process repeatedly several times since the
>  initial replication started (and the first slave finished) nine days ago.

Which indicates that an error is occurring during the subscription process.

Either the slon logs or pg logs on the affected slave will indicate the problem.

>  Question:  does updates of some of the tables on the origin during the
>  initial replication have a bearing on this?  One of the parent tables on
>  the master is regularly updated, but the other tables are not.

No, you can update away on the master while subscribing slaves.

>  test_slony_state.pl reports that "pg_listener relpages high -
>  6460"..."Perhaps a long running transaction is preventing pg_listener from
>  being vacuumed out?"   Presumably this is just a side-effect of the
>  initial replication?  Anyway, I did a vacuum full analyze on pg_listener
>  on all the nodes since it couldn't hurt.  After that vacuum, the report
>  says "pg_listener reltuples high - 346307"... :-)))

This is probably because it has been trying to replicate and faiing -
in the mean time it is queuing up all the changes in the master
database.

>  I can provide more config detail if required (plus output from
>  test_slony_state.pl).

Please provide as much detail as possible. You haven't even told us
what version of PostgreSQL you are running and only accidently told us
what version of Slony because it was in a log snippet.

-Dave