> One last thing - do you think there is any need to mention this > behaviour in the pgdocs, or is OK just to be a hidden performance > improvement?
FYI - I put my opinion. We have following sentence in the logical-replication.sgml:
``` ... If the table does not have any suitable key, then it can be set to replica identity <quote>full</quote>, which means the entire row becomes the key. This, however, is very inefficient and should only be used as a fallback if no other solution is possible. ... ```
Here the word "very inefficient" may mean that sequential scans will be executed every time. I think some descriptions can be added around here.
Making a small edit in that file makes sense. I'll attach v13 in the next email that also includes this change.
Also, do you think is this a good time for me to mark the patch "Ready for committer" in the commit fest? Not sure when and who should change the state, but it seems I can change. I couldn't find any documentation on how that process should work.
