Thanks, Gordon! I did restart the slon process on the subscriber, maybe that helped me get it going.
I appreciate your reply. Do you have an automated process or do you do it manually? Best, -at On Mon, Mar 29, 2010 at 4:38 PM, Gordon Shannon <[email protected]> wrote: > I also run 2.0.2 and I see this all the time. I just bounce the slon > process for the subscriber and that gets it going. > > Gordon > > On Mon, Mar 29, 2010 at 3:27 PM, Aleksey Tsalolikhin > <[email protected]> wrote: >> >> Hi. I am trying to get Slony 2.0.2 up for the first time between two >> Postgres 8.4 instances, and the data copy is failing with "could not >> lock table $tablename on subscriber". >> >> Connected to provider DB. >> Prepare to copy table. >> Could not lock table ${name of first table} on subscriber. >> Data copy for set 1 failed. >> >> All the tables on the slave are empty. >> >> I am using 'postgres' for the replication user. >> >> I checked with "select * from pg_stat_activity;" on the slave and it >> shows all sessions are IDLE. >> >> Any suggestions for getting the initial copy going? >> >> Thanks, >> Aleksey >> _______________________________________________ >> Slony1-general mailing list >> [email protected] >> http://lists.slony.info/mailman/listinfo/slony1-general > > > > -- > If I had more time, I could have written you a shorter letter. (Blaise > Pascal) > _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
