Maybe I wasn't clear on what was failing, the replication itself seems to be working fine - the 'subscribe set' worked and data appeared to be flowing.
What failed was a _separate_ application that was importing data into the master database, this application was using a non-superuser account to insert data into one of the tables in the replication set, and it was this process that saw the 'permission denied for sequence sl_action_seq' error. Thanks, David. Mark Stosberg wrote: > David Brain wrote: >> Hi, >> >> I set up what would appear to be a fairly simple replication between >> (large - multi GB) data bases. Replication appears to start fine. >> >> However I experienced problems inserting data into the master database >> during the initial copy process. The error was: >> >> 'permission denied for sequence sl_action_seq' >> >> The process doing the insert was using a different user (with less >> permissions) than the replication (which is using the postgres user). >> >> I did not see anything about this in the documentation, but presumably I >> also need to grant permissions to the inserting user on the Slony >> tables/sequences. > > That hasn't been my experienced. > > It's my understanding that the "subscribe set" command, which does the > initial copy, is also to be done as a super-user. > > However, I'm fairly new here myself, so you may wait for a second opinion. > -- David Brain - bandwidth.com [EMAIL PROTECTED] 919.297.1078 _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
