On Fri, May 01, 2009 at 06:43:18AM -0700, Melvin Davidson wrote:
> 2009-04-29 09:42:45 EDT ERROR  cleanupThread: " analyze "_mas_rep".sl_seqlog;" - 2009-04-29 09:42:45 EDT DEBUG1 cleanupThread:  analyze
>  "_mas_rep".sl_archive_counter;
> 2009-04-29 09:42:45 EDT ERROR  cleanupThread: " analyze "_mas_rep".sl_archive_counter;" - 2009-04-29 09:42:45 EDT DEBUG1 cleanupThread:  analyze "pg_catalog".pg_listener;
> 2009-04-29 09:42:45 EDT ERROR  cleanupThread: " analyze "pg_catalog".pg_listener;" - 2009-04-29 09:42:45 EDT DEBUG1 cleanupThread:  analyze "pg_catalog".pg_statistic;
> 2009-04-29 09:42:45 EDT ERROR  cleanupThread: " analyze "pg_catalog".pg_statistic;" - 2009-04-29 09:42:45 EDT INFO   cleanupThread:    0.007 seconds for vacuuming
> 
> I still have no clue as to why this is occurring. These errors are only reported in the slony log, The postgres log shows nothing related.
> 

What's your log level in Postgres?  Also, I don't see what the actual
error is here.  Maybe Slony's just reporting what ought to be INFO on
the ERROR channel?

A

-- 
Andrew Sullivan
ajs at crankycanuck.ca