diff options
| author | Peter Eisentraut | 2018-02-17 01:44:15 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2018-03-16 17:18:06 +0000 |
| commit | 04700b685f31508036456bea4d92533e5ceee9d6 (patch) | |
| tree | f3fc6cddf9f5764decbaa76c5c5423fdcd873a36 /src/backend/commands/portalcmds.c | |
| parent | 8d47a908626bf0800dc6a01f4ff2b2bc15cdaf86 (diff) | |
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 <[email protected]>
Diffstat (limited to 'src/backend/commands/portalcmds.c')
| -rw-r--r-- | src/backend/commands/portalcmds.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/commands/portalcmds.c b/src/backend/commands/portalcmds.c index 6ecaea14433..73821502ba6 100644 --- a/src/backend/commands/portalcmds.c +++ b/src/backend/commands/portalcmds.c @@ -63,7 +63,7 @@ PerformCursorOpen(DeclareCursorStmt *cstmt, ParamListInfo params, * user-visible effect). */ if (!(cstmt->options & CURSOR_OPT_HOLD)) - RequireTransactionChain(isTopLevel, "DECLARE CURSOR"); + RequireTransactionBlock(isTopLevel, "DECLARE CURSOR"); /* * Parse analysis was done already, but we still have to run the rule |
