PL/pgSQL RETURN NEXT was leaking converted tuples, causing
out of memory when looping through large numbers of rows. Flag the converted tuples to be freed. Complaint and patch by Joe.
This commit is contained in:
parent
56c8d50eaf
commit
564b257e44
@ -2221,6 +2221,7 @@ exec_stmt_return_next(PLpgSQL_execstate *estate,
|
||||
{
|
||||
tuple = do_convert_tuple(tuple, tupmap);
|
||||
free_conversion_map(tupmap);
|
||||
free_tuple = true;
|
||||
}
|
||||
}
|
||||
break;
|
||||
|
Loading…
x
Reference in New Issue
Block a user