diff options
| author | Andres Freund <andres@anarazel.de> | 2018-11-13 12:18:25 -0800 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2018-11-15 11:40:50 -0800 |
| commit | c058fc2a2b8ea25015b211186c88a6a3006f5937 (patch) | |
| tree | 32c71bf0a7ce90d86c32b500bb2e27c6118d3dd3 /src/backend/executor/nodeHashjoin.c | |
| parent | 6a744413ea0c0c114348c4c010aa9f909c83d3f3 (diff) | |
| download | postgresql-c058fc2a2b8ea25015b211186c88a6a3006f5937.tar.gz postgresql-c058fc2a2b8ea25015b211186c88a6a3006f5937.zip | |
Rationalize expression context reset in ExecModifyTable().
The current pattern of reseting expressions both in
ExecProcessReturning() and ExecOnConflictUpdate() makes it harder than
necessary to reason about memory lifetimes. It also requires
materializing slots unnecessarily, although this patch doesn't take
advantage of the fact that that's not necessary anymore.
Instead reset the expression context once for each input tuple.
Author: Ashutosh Bapat
Discussion: https://postgr.es/m/20181105210039.hh4vvi4vwoq5ba2q@alap3.anarazel.de
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions