On 11/11/2004 1:40 AM, Hannu Krosing wrote:

>> 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
> ...
>>> "_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.
> 
> Yes, that would be much better than the current situation.
> 
> But back to my original question - is there a way to disable the vacuuming
> altogether ?

There's no commandline or config option at the moment. But hacking 
cleanup_thread.c might be easy enough to get the desired effect.


Jan

> 
> For example to avoid having ERRORS:s in the log .
> 
> -----------------
> Hannu


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