From 04700b685f31508036456bea4d92533e5ceee9d6 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 16 Feb 2018 20:44:15 -0500 Subject: Rename TransactionChain functions We call this thing a "transaction block" everywhere except in a few functions, where it is mysteriously called a "transaction chain". In the SQL standard, a transaction chain is something different. So rename these functions to match the common terminology. Reviewed-by: Alvaro Herrera --- src/backend/commands/cluster.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/backend/commands/cluster.c') diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c index 5d481dd50de..96a51bb7603 100644 --- a/src/backend/commands/cluster.c +++ b/src/backend/commands/cluster.c @@ -202,7 +202,7 @@ cluster(ClusterStmt *stmt, bool isTopLevel) * We cannot run this form of CLUSTER inside a user transaction block; * we'd be holding locks way too long. */ - PreventTransactionChain(isTopLevel, "CLUSTER"); + PreventInTransactionBlock(isTopLevel, "CLUSTER"); /* * Create special memory context for cross-transaction storage. -- cgit v1.2.3