Don't do logical replication of TRUNCATE of zero tables When due to publication configuration, a TRUNCATE change ends up with zero tables to be published, don't send the message out, just skip it. It's not wrong, but obviously useless overhead.
Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/92e1583b439ffab1d20419998895932e4fbe32fd Modified Files -------------- src/backend/replication/pgoutput/pgoutput.c | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-)
