<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Sep 30, 2014, at 5:05 PM, Jeff Frost <<a href="mailto:jeff@pgexperts.com">jeff@pgexperts.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>On Sep 30, 2014, at 5:03 PM, Greg Sabino Mullane <<a href="mailto:greg@endpoint.com">greg@endpoint.com</a>> wrote:<br><br><blockquote type="cite">On Tue, Sep 30, 2014 at 03:18:42PM -0700, Jeff Frost wrote:<br><blockquote type="cite">Seeing this error from finishTableAfterCopy:<br><br>PGRES_FATAL_ERROR ERROR: permission denied for relation pg_class<br><br>slony 2.1.4 connecting to postgresql 9.2.9 as the slony user which is a postgresql superuser.<br><br></blockquote>...<br><blockquote type="cite">rolname | slony<br>rolsuper | t<br></blockquote><br>At the risk of stating the obvious, triple check the right role is<span class="Apple-converted-space"> </span><br>being used. If your log_line_prefix has a %u, check that in the<span class="Apple-converted-space"> </span><br>error message. Or try dropping the slony user and try rerunning.<span class="Apple-converted-space"> </span><br>If that gives the expected error, double check it has rolsuper /and/<span class="Apple-converted-space"> </span><br>rolcatupdate set.<br></blockquote><br>Yah, we log to csvlog and it's definitely using the slony user. <br><br>I already tried dropping and recreating the role and the slon was unable to connect until the role was recreated; however, still the same issue with the newly created superuser role.<br><br></div></blockquote><div><br></div>Figured it out.</div><div><br></div><div>The ownership of the functions in the slony schema got reassigned.</div><div><br></div><div>Assigning them back to the slony user made it happy again.</div><div><br><br></div><br></body></html>