On Wednesday November 10 2004 3:56, Hannu Krosing wrote:
> I (think I) need to disable slons vacuuming of my autovacuum-managed
> database
>
> My problem is that sometimes slon just gets error 'concurrent update'
> (and exits) and tells me about concurrent vacuum being run there.

Funny you should mention that.  We have same issue.

FATAL  cleanupThread: "vacuum analyze "_replication".sl_event; vacuum 
analyze "_replication".sl_confirm; vacuum analyze 
"_replication".sl_setsync; vacuum analyze "_replication".sl_log_1; vacuum 
analyze "_replication".sl_log_2;vacuum analyze 
"_replication".sl_seqlog;vacuum analyze pg_catalog.pg_listener;" - ERROR:  
simple_heap_update: tuple concurrently updated


My understanding is that this is harmless.  Is that right?

If so, just wondering if slon really needs to exit?

Ed