From: | Sayan Biswas <formal(dot)sayan(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Modifying Postgresql Optimizer to select optimal memory |
Date: | 2014-04-01 17:23:55 |
Message-ID: | CAPfq5ZW5MBafwg984-CwgfyG54M2zDWreYv=s3Nom=iSbCR9Rw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello everyone,
We are currently working on a DBMS course project that requires us to
modify postgresql optimizer. We need to vary work_mem within a range and
note down the cost at those points(allocated memory) after 'explain'
operation and then select the optimal tradeoff. We were changing
"postgresql-9.1.12/src/backend/optimizer/plan/planner.c" where we created a
new function mem_tradeoff() that calls planner() within a for loop for the
varying memory. This mem_tradeoff() is called from pg_plan_query() in
"postgresql-9.1.12/src/backend/tcop/postgres.c". The problem is, if the for
loop runs only one iteration, everything is fine, but if we print
plan->planTree->total_cost, it is printed 132 times for any query. Also if
the for loop runs more than one iteration, we get a segmentation fault. Any
help is very much appreciated.
Thank you,
Sayan
--
Don't kill the dream - execute it.
From | Date | Subject | |
---|---|---|---|
Next Message | Si Chen | 2014-04-01 19:51:05 | simple update query stuck |
Previous Message | Dev Kumkar | 2014-04-01 14:45:45 | Re: RHEL 7 and Postgres 9.3.4 |