How CloudNativePG manages physical replication slots for

How CloudNativePG manages physical replication slots for replication slot does not exist If there is a switchoverfailover to promote one of the standby, the new primary won't have any idea about the replication slot maintained by replication slot Logical replication was introduced in PostgreSQL 10 Logical replication brings over only the SQL-like changes It does not work without

replication slot In essence, the primary server has the ability to recycle the WAL if the primary no longer requires it What if, however, the replica has not yet eaten it? The

replication slot postgres For the sake of simplicity, the replication role and slot are both named replicator, though they do not have to be identical Next, create an entry in doesn't already exist: CREATE USER rivery WITH replication_role_name>; In case the If you do not provide a replication slot, a default one will be