On 11/10/2004 7:21 PM, Ed L. wrote:

> 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?

Now that you say it ... it doesn't have to exit. An immediate retry and 
reconnecting if that would error as well would certainly do the job.


Jan

> 
> Ed
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #