On Tue, Jun 11, 2019 at 12:26 PM Christopher Browne <cbbrowne at afilias.info>
wrote:

>
>
> On Tue, Jun 11, 2019 at 1:30 PM Tory M Blue <tmblue at gmail.com> wrote:
>
>> I'm wondering if there is anything I can do to prevent what appears to be
>> slony replication backup (not replicating) during a pg_dump. I'm using a -N
>> slonschema, so wondering if there is any other techniques to prevent slon
>> replication delay during pg_dumps?
>>
>
> Hmm.  I remember the "big deal" being to ensure that the Slony schema was
> left out, as that would definitely lead to locking that would cause
> replication to fall behind.
>
> It's possible that something new has come along that would lock in a
> troublesome way.
>
> I suggest that you take a look in pg_catalog.pg_locks to see what objects
> Slony is waiting on, thus, looking for:
>
>   select * from pg_catalog.pg_locks where not granted;
>
> Some further work needs to be done to trace that to exactly what objects
> are locked.
>

Ya will take a look, I also thought that bypassing the slon schema would
solve it but apparently not, we can have 2-10million count in the sl_log
before it clears and it's apparent that the replication is not happening,
so I'll poke around some more. Glad to see folks are still around :)

Thanks
Tory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20190611/c0ec2858/attachment.htm