What happens to logical replication after running pg_upgrade?

Now a common cause for this kind of issue are replication slots which are not advanced: in that case, Postgres will hold on to all WAL segments

What happens to logical replication after running pg_upgrade? Fixing PostgreSQL database replication errors · Removing an inactive replication slot · Message: WARNING: oldest xmin is far in the past and pg_wal size growing

Now a common cause for this kind of issue are replication slots which are not advanced: in that case, Postgres will hold on to all WAL segments

tree slot catalog_xmin, xid, The oldest transaction affecting the system catalogs that this slot needs the database to retain VACUUM cannot remove catalog tuples deleted

My understanding is that the replication slot prevents it from deleting that log, right? Until both the standby and

delete national lottery account SELECT pg_drop_replication_slot; Replace 'slot_name' with the name of the replication slot you want to remove Clean Up:

Learn how to use replication slots with PostgreSQL's streaming physical replication drop a slot psql -c select * from pg_drop_replication_slot('replica