|
| Hi Hannu,
I just run VACUUM before doing the copy dump, because I knew that this
could behave strange without a VACUUM before.
I will make the same dump today again and see what happens - maybe the
cause was somewhere else and not slony related - as you said.
Hannu Krosing wrote:
> On L, 2005-09-24 at 18:32 +0100, Aldor wrote:
>
>
> ...
>
>
>
> Are you running this on live db, i.e. are these other tables actively
> updated and replicated ?
>
> How long is the time for loading the dumps ?
>
>
>
>
> Slony triggers should not directly affect the tables they are *not* used
> on.
>
> For longer transactions, when tables pg_listener, sl_log_1 and others
> start to grow into megabytes in size, queries issued by slon can
> sometimes misbehave, eat tons of CPU, wait for several minutes for locs
> on pg_listener and do other bad things bogging the whole database down.
>
> But this is through secondary effects of *any* long transactions, not
> the slony *triggers* on unrelated tables.
>
> OTOH, you may be just some effects of not having run vacuum or analyse
> often enough resulting in sharp performance drop, completely unrelated
> to slony.
>
|
|