I don't know if this applies only to pglogical or logical decoding in
general. This is on a 9.6.10 provider running pglogical 2.2.0. Subscriber
has same versions. We had a replication delay situation this morning,
which I think may have been due to a really long transaction but I've yet
to verif
On December 8, 2018 9:08:09 AM PST, Jeremy Finzel wrote:
>I don't know if this applies only to pglogical or logical decoding in
>general. This is on a 9.6.10 provider running pglogical 2.2.0.
>Subscriber
>has same versions. We had a replication delay situation this morning,
>which I think ma
>
> That doesn't indicate an error. You need to provide more details what
> made you consider things wedged...
>
> Andres
>
Thank you very much for the reply. We typically see no visible replication
delay over 5 minutes ever. Today we saw a delay of over 3 hours, and no
obvious increase in work
On Sat, Dec 8, 2018 at 1:21 PM Jeremy Finzel wrote:
> That doesn't indicate an error. You need to provide more details what
>> made you consider things wedged...
>>
>> Andres
>>
>
> Thank you very much for the reply. We typically see no visible
> replication delay over 5 minutes ever. Today we
On 12/8/18 8:21 PM, Jeremy Finzel wrote:
There are 2.1 million files in pg_replslot which I don't think is
normal? Any ideas as to where I should be looking or what could cause this?
Postgres spills changes on disk when you have a big transaction:
https://blog.anayrat.info/en/2018/03/10/logic
