Hi Justin, thanks for the response! > REPLICA IDENTITY DEFAULT will only use primary keys, if the publisher > includes those tables, the subscriber when replaying the WAL will stop > throwing an error not knowing how to replay the UPDATE/DELETE.
But I don't see any errors being thrown out in the postgresql logs? Should I be seeing it complain there? Is postgresql falling back to replica identity full here? However I checked that table, it doesn't seem to be making progress at all: so I suspect you are right that it is the problem. > Logical Replication is most likely broken at this point. > > I suggest stopping logical replication and correcting tables that don't have > qualifying indexes for logical replication by creating the necessary indexes > and avoid using replica identity full. Then restart logical replication from > the beginning. > >
