diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2018-04-05 14:51:56 -0400 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2018-04-05 14:51:56 -0400 |
| commit | b9986551e0c6129300b9d7a387baf2006724b297 (patch) | |
| tree | dbb5abc11a64be98d0ad79470eea5b9ce9638fc5 /src/backend/parser/parse_clause.c | |
| parent | 6a5f796b48b0e9808fef9731da8aea17f56de999 (diff) | |
| download | postgresql-b9986551e0c6129300b9d7a387baf2006724b297.tar.gz postgresql-b9986551e0c6129300b9d7a387baf2006724b297.zip | |
Fix plan cache issue in PL/pgSQL CALL
If we are not going to save the plan, then we need to unset expr->plan
after we are done, also in error cases. Otherwise, we get a dangling
pointer next time around.
This is not the ideal solution. It would be better if we could convince
SPI not to associate a cached plan with a resource owner, and then we
could just save the plan in all cases. But that would require bigger
surgery.
Reported-by: Pavel Stehule <pavel.stehule@gmail.com>
Diffstat (limited to 'src/backend/parser/parse_clause.c')
0 files changed, 0 insertions, 0 deletions