ExeMgr memory leak when joining and using limit

Bug #487346 reported by wweeks on 2009-11-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
InfiniDB Community
Fix Released

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.

wweeks (wweeks) on 2009-11-23
Changed in infinidb:
importance: Undecided → Medium
status: New → Confirmed
wweeks (wweeks) on 2009-11-24
Changed in infinidb:
status: Confirmed → In Progress
Revision history for this message
wweeks (wweeks) wrote :

Resolved in The remaining rows are now consumed in the connector connector when a limit clause is used.

Changed in infinidb:
milestone: none → 0.9.5
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers