Open debugger22 opened 1 month ago
It's happening with large tables
Sometimes it also throws - failed to set transaction snapshot: failed to set transaction snapshot: ERROR: invalid snapshot identifier: "0000000E-0002EEB6-1" (SQLSTATE 22023)
I've seen this happen when the initial copy gets interrupted. In that scenario we should get a new snapshot
Is peerdb running out of memory on your setup?
Hi @debugger22 ! Could happen if peerdb - specifically the flow-snapshot-worker container - restarts. That container needs to always be up during initial load. Is it possible to check if that container ever went down?
[pg_query_executor] failed to set snapshot: ERROR: invalid snapshot identifier: "0000002F-00040D68-1" (SQLSTATE 22023)