aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2018-11-13 08:59:41 +0900
committerMichael Paquier <michael@paquier.xyz>2018-11-13 08:59:41 +0900
commit52b70b1c7df5929465cf3dd8f4798e6f2e204f61 (patch)
tree416427d145df00e118f0df61e7982372638072bc
parent3de491482b6c815a2e735dbbb8972e0907d75188 (diff)
downloadpostgresql-52b70b1c7df5929465cf3dd8f4798e6f2e204f61.tar.gz
postgresql-52b70b1c7df5929465cf3dd8f4798e6f2e204f61.zip
Remove CommandCounterIncrement() after processing ON COMMIT DELETE
This comes from f9b5b41, which is part of one the original commits that implemented ON COMMIT actions. By looking at the truncation code, any CCI needed happens locally when rebuilding indexes, so it looks safe to just remove this final incrementation. Author: Michael Paquier Reviewed-by: Álvaro Herrera Discussion: https://postgr.es/m/20181109024731.GF2652@paquier.xyz
-rw-r--r--src/backend/commands/tablecmds.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/src/backend/commands/tablecmds.c b/src/backend/commands/tablecmds.c
index 82989158eeb..946119fa860 100644
--- a/src/backend/commands/tablecmds.c
+++ b/src/backend/commands/tablecmds.c
@@ -13334,10 +13334,8 @@ PreCommit_on_commit_actions(void)
* exists at truncation time.
*/
if (oids_to_truncate != NIL)
- {
heap_truncate(oids_to_truncate);
- CommandCounterIncrement(); /* XXX needed? */
- }
+
if (oids_to_drop != NIL)
{
ObjectAddresses *targetObjects = new_object_addresses();