Bill,
Sorry about that, I didn't see that the answer was just for you.

Bill,
You said that VACUUM FULLs are not an effective method of ongoing
maintenance. But VACUUM FULL is used by more than 5 years, so VACUUM is a
culture in the company. The DBA function is new in the company, and I have
been reading everything I find about Postgres, DB, Slony, Maintenance, and
so on.
I would like to know if you could pass me a forum or a list of messages on
Postgres or maintenance in DB.
If you can, I would be very grateful.

People,
I'll give a new search in the documentation to find something about slony's
vacuum and how to stop that.
The problem is that I have an external application, and when the Slony's
vacuum is running the application begins to slow down and give time-out.
I think necessary to run the vacuum when it asks, but while the company
decides not replace the hardware, I have to do that anyway. However, they
are warned that this could affect the replication.

If someone discover how to do that I thank you very much.

I thank all.
Rafael Domiciano


2008/5/22 salman <salmanb at quietcaresystems.com>:

>
>
> Christopher Browne wrote:
>
>> "Rafael Domiciano" <rafael.domiciano at gmail.com> writes:
>>
>>> Frequently Slony is vacuuming my database, and I'm having to kill his
>>> proccess because it's slowing the client-side application.
>>> I tryied to find option that disables the vacuum but i'm unsucessful.
>>> Someone know how to stop vacuum's Slony?
>>>
>>
>>
> Not sure what kind of a shop you run and how many inserts/updates/deletes
> you do during a day -- we do about 5.5M inserts a day, and we archive ~3-=
4M
> records a day (dumped to disk, removed from production db) and the slony
> vacuum jobs do not slow anything down for us.
>
> The only time we have slowdown is when one particular script leaves an
> 'idle in transaction' query open for a number of hours -- once that happe=
ns,
> slony's fetch requests and the growing log table really drag the server
> down. But, the problem isn't created by slony here, obviously, it's one of
> our scripts.
>
> -salman
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080526/=
d1dd6aee/attachment.htm