| From: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
|---|---|
| To: | Rajmohan C <csrajmohan(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Planner hints in Postgresql |
| Date: | 2014-03-17 15:55:41 |
| Message-ID: | CAOeZVifr=qsqPRtUYRj05GjVzy_FXoOSdc7o42jSKPe6OU0F3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 17, 2014 at 9:22 PM, Rajmohan C <csrajmohan(at)gmail(dot)com> wrote:
> I am implementing Planner hints in Postgresql to force the optimizer to
> select a particular plan for a query on request from sql input. I am having
> trouble in modifying the planner code. I want to create a path node of hint
> plan and make it the plan to be used by executor. How do I enforce this ?
> Should I create a new Plan for this ..how to create a plan node which can
> be then given directly to executor for a particular query?
>
Planner hints have been discussed a lot before as well and AFAIK there is a
wiki page that says why we shouldnt implement them. Have you referred to
them?
Please share if you have any new points on the same.
Regards,
Atri
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-03-17 15:56:04 | Re: HEAD seems to generate larger WAL regarding GIN index |
| Previous Message | Rajmohan C | 2014-03-17 15:52:21 | Planner hints in Postgresql |