Logical replication - restart_lsn resets back and the status becomes 'unreserved'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



We have a case where the customer does CDC using peer db and logical replication. For what ever reason, the restart_lsn on the publisher is reversed and goes so much back that the 'WAL' for that lsn is no longer available on the disk. At which point the status of the replication slot becomes 'unreserved' and at the next checkpoint terminates the slot. It errors out with 
` invalidating slot "<<slot_name>>" because its restart_lsn 622D/1E244A08 exceeds max_slot_wal_keep_size"

We do not set max_slot_wal_keep_size, it is at the default of -1.

Any insights on what conditions would restart_lsn actually is reversed and any insights on how to trace the request coming into the publisher when it updates pg_replication_Slots?

Thank You

[Index of Archives]     [Postgresql Home]     [Postgresql General]     [Postgresql Performance]     [Postgresql PHP]     [Postgresql Jobs]     [PHP Users]     [PHP Databases]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Yosemite Forum]

  Powered by Linux