Hello hackers, It seems there is a pattern how the error is occurring in different systems. Following are the relevant log snippets:
nightjar: sub3 LOG: received replication command: CREATE_REPLICATION_SLOT "sub3_16414_sync_16394" TEMPORARY LOGICAL pgoutput USE_SNAPSHOT sub3 LOG: logical decoding found consistent point at 0/160B578 sub1 PANIC: could not open file "pg_logical/snapshots/0-160B578.snap": No such file or directory dromedary scenario 1: sub3_16414_sync_16399 LOG: received replication command: CREATE_REPLICATION_SLOT "sub3_16414_sync_16399" TEMPORARY LOGICAL pgoutput USE_SNAPSHOT sub3_16414_sync_16399 LOG: logical decoding found consistent point at 0/15EA694 sub2 PANIC: could not open file "pg_logical/snapshots/0-15EA694.snap": No such file or directory dromedary scenario 2: sub3_16414_sync_16399 LOG: received replication command: CREATE_REPLICATION_SLOT "sub3_16414_sync_16399" TEMPORARY LOGICAL pgoutput USE_SNAPSHOT sub3_16414_sync_16399 LOG: logical decoding found consistent point at 0/15EA694 sub1 PANIC: could not open file "pg_logical/snapshots/0-15EA694.snap": No such file or directory While subscription 3 is created, it eventually reaches to a consistent snapshot point and prints the WAL location corresponding to it. It seems sub1/sub2 immediately fails to serialize the snapshot to the .snap file having the same WAL location. Is this helpful? -- Thanks & Regards, Kuntal Ghosh EnterpriseDB: http://www.enterprisedb.com
