> If you are replicating changes from only a few tables, ensure that you create a PUBLICATION that includes just those tables. Postgres efficiently persists changes for only those tables in the replication slot. This helps reduce the size of the replication slot and improves logical decoding performance.
I didn't think the replication slot "stored" changes. I thought it just had a WAL position to hold on to and filtering was done by WAL sender (so it helps reduce outgoing traffic but not retained WAL)
where is this coming from?