Thu Nov 11 06:40:39 PST 2004
- Previous message: [Slony1-general] How to disable slon from vacuuming database managed by autovacuum
- Next message: [Slony1-general] How to disable slon from vacuuming databasemanaged by autovacuum
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 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 ? For example to avoid having ERRORS:s in the log . ----------------- Hannu
- Previous message: [Slony1-general] How to disable slon from vacuuming database managed by autovacuum
- Next message: [Slony1-general] How to disable slon from vacuuming databasemanaged by autovacuum
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list