Skip to content

Commit 52b70b1

Browse files
committed
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
1 parent 3de4914 commit 52b70b1

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

src/backend/commands/tablecmds.c

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13334,10 +13334,8 @@ PreCommit_on_commit_actions(void)
1333413334
* exists at truncation time.
1333513335
*/
1333613336
if (oids_to_truncate != NIL)
13337-
{
1333813337
heap_truncate(oids_to_truncate);
13339-
CommandCounterIncrement(); /* XXX needed? */
13340-
}
13338+
1334113339
if (oids_to_drop != NIL)
1334213340
{
1334313341
ObjectAddresses *targetObjects = new_object_addresses();

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy