]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e348e7a) | patch
Don't do logical replication of TRUNCATE of zero tables
authorPeter Eisentraut <peter_e@gmx.net>
Mon, 30 Apr 2018 17:49:20 +0000 (13:49 -0400)
committerPeter Eisentraut <peter_e@gmx.net>
Mon, 30 Apr 2018 17:49:20 +0000 (13:49 -0400)
commit92e1583b439ffab1d20419998895932e4fbe32fd
tree0694cf062f71d19ba00fb3b7f516e0272a488c08tree | snapshot
parente348e7ae5727a6da8678036d748e5c5af7deb6c9commit | diff
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.
src/backend/replication/pgoutput/pgoutput.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.