Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit b351eba

Browse files
committed
Add comment about the two different query strings that ExecuteQuery()
has to deal with.
1 parent 5618ece commit b351eba

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

src/backend/commands/prepare.c

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
* Copyright (c) 2002-2008, PostgreSQL Global Development Group
1111
*
1212
* IDENTIFICATION
13-
* $PostgreSQL: pgsql/src/backend/commands/prepare.c,v 1.88 2008/07/18 20:26:06 tgl Exp $
13+
* $PostgreSQL: pgsql/src/backend/commands/prepare.c,v 1.89 2008/07/21 15:26:55 tgl Exp $
1414
*
1515
*-------------------------------------------------------------------------
1616
*/
@@ -162,6 +162,12 @@ PrepareQuery(PrepareStmt *stmt, const char *queryString)
162162

163163
/*
164164
* Implements the 'EXECUTE' utility statement.
165+
*
166+
* Note: this is one of very few places in the code that needs to deal with
167+
* two query strings at once. The passed-in queryString is that of the
168+
* EXECUTE, which we might need for error reporting while processing the
169+
* parameter expressions. The query_string that we copy from the plan
170+
* source is that of the original PREPARE.
165171
*/
166172
void
167173
ExecuteQuery(ExecuteStmt *stmt, const char *queryString,

0 commit comments

Comments
 (0)