Open mikecann opened 1 year ago
Looks like it was due to the WAL replication slots I was also experimenting around with.
I have now deleted those slots and the error no longer shows.
There may however be a better way of handling this?
Nope, its still happening.. :(
This is happening because the archive table doesn't have a primary key defined.
Hi,
Im experimenting around with pg-boss as a replacement for our redis based queue and am getting the following error periodically:
Im assuming this is happening on a schedule as part of some maintenance job PGBoss is doing but im not sure what it is in my DB that might be causing it.
Any ideas?