On Wed, Oct 19, 2022 at 03:16:59PM +0530, Amit Kapila wrote:
> Yeah, as requested yesterday, maybe checking if this can be reproduced
> will help us to narrow down the cause. If this doesn't happen due to
> an application mistake it appears that after the slot becomes inactive
> during the time walsender was down, the server removes the required
> files but there is nothing in the code that suggests that such a thing
> can happen.
> Are there any more logs on publisher/subscriber which indicate any
> sort of error?
This specific setup of replication was torn down, we couldn't keep it
running. Can setup it once more, and with some luck it will break again.
Will take a day, though.
Is there anything I can do to make it more debugable, but that will not
require restart of pg12?
Best regards,
depesz
