ExeMgr memory leak when joining and using limit
Bug #487346 reported by
wweeks
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
InfiniDB Community |
Fix Released
|
Medium
|
Unassigned |
Bug Description
ExeMgr is leaking memory when joining and the query uses a limit clause. Here's an example query that reproduces the problem against the tpch database.
select o_orderkey, o_orderdate, c_acctbal, c_nationkey, o_shippriority,
o_totalprice, o_clerk, c_comment from orders, customer where o_custkey =
c_custkey limit 0,30;
ExeMgr memory usage climbs with each repeated run of the query.
Changed in infinidb: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in infinidb: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Resolved in 0.9.5.2. The remaining rows are now consumed in the connector connector when a limit clause is used.