On Sep 30, 2014, at 5:05 PM, Jeff Frost <jeff at pgexperts.com> wrote:

> 
> On Sep 30, 2014, at 5:03 PM, Greg Sabino Mullane <greg at endpoint.com> wrote:
> 
>> On Tue, Sep 30, 2014 at 03:18:42PM -0700, Jeff Frost wrote:
>>> Seeing this error from finishTableAfterCopy:
>>> 
>>> PGRES_FATAL_ERROR ERROR:  permission denied for relation pg_class
>>> 
>>> slony 2.1.4 connecting to postgresql 9.2.9 as the slony user which is a postgresql superuser.
>>> 
>> ...
>>> rolname        | slony
>>> rolsuper       | t
>> 
>> At the risk of stating the obvious, triple check the right role is 
>> being used. If your log_line_prefix has a %u, check that in the 
>> error message. Or try dropping the slony user and try rerunning. 
>> If that gives the expected error, double check it has rolsuper /and/ 
>> rolcatupdate set.
> 
> Yah, we log to csvlog and it's definitely using the slony user.  
> 
> 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.
> 

Figured it out.

The ownership of the functions in the slony schema got reassigned.

Assigning them back to the slony user made it happy again.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20140930/94ffd19c/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 208 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.slony.info/pipermail/slony1-general/attachments/20140930/94ffd19c/attachment.pgp