Outdated comments around HandleFunctionRequest
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Heikki Linnakangas <hlinnaka@iki.fi>, pgsql-hackers@postgresql.org
Date: 2017-04-05T01:05:25Z
Lists: pgsql-hackers
Hi,
PostgresMain() has the following blurb for fastpath functions:
/*
* Note: we may at this point be inside an aborted
* transaction. We can't throw error for that until we've
* finished reading the function-call message, so
* HandleFunctionRequest() must check for it after doing so.
* Be careful not to do anything that assumes we're inside a
* valid transaction here.
*/
and in HandleFunctionRequest() there's:
* INPUT:
* In protocol version 3, postgres.c has already read the message body
* and will pass it in msgBuf.
* In old protocol, the passed msgBuf is empty and we must read the
* message here.
which is not true anymore. Followed by:
/*
* Now that we've eaten the input message, check to see if we actually
* want to do the function call or not. It's now safe to ereport(); we
* won't lose sync with the frontend.
*/
which is also not really meaningful, because there's no previous code in
the function.
This largely seems to be damage from
commit 2b3a8b20c2da9f39ffecae25ab7c66974fbc0d3b
Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date: 2015-02-02 17:08:45 +0200
Be more careful to not lose sync in the FE/BE protocol.
Heikki?
- Andres
Commits
-
Remove dead code and fix comments in fast-path function handling.
- f2389f119f52 9.2.21 landed
- c2f08c642945 9.3.17 landed
- 88101abe70cb 9.4.12 landed
- 39cedd8d9593 9.5.7 landed
- b3721f7d13aa 9.6.3 landed
- fd01983594b7 10.0 landed
-
Be more careful to not lose sync in the FE/BE protocol.
- 2b3a8b20c2da 9.5.0 cited