From: | decibel <decibel(at)decibel(dot)org> |
---|---|
To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | pgsql-general(at)postgresql(dot)org, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: contrib/plantuner - enable PostgreSQL planner hints |
Date: | 2009-10-16 17:04:28 |
Message-ID: | 47E63672-972E-452C-AFBE-37C3C883D9FC@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Oct 6, 2009, at 2:57 PM, Oleg Bartunov wrote:
> this is an announcement of our new contribution module for
> PostgreSQL - Plantuner - enable planner hints
> (http://www.sai.msu.su/~megera/wiki/plantuner)
>
> =# set enable_seqscan=off;
> =# set plantuner.forbid_index='id_idx2';
Out of curiosity, did you look at doing hints as comments in a query?
I'm guessing you couldn't actually do that in just a contrib module,
but it's how Oracle handles hints, and it seems to be *much* more
convenient, because a hint only applies for a specific query. I think
it's extremely unlikely you would intentionally want the same hint to
apply to a bunch of queries, and extremely likely that you could
accidentally forget to re-enable something.
That said, thanks for contributing this!
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
From | Date | Subject | |
---|---|---|---|
Next Message | Kirk Wythers | 2009-10-16 17:25:17 | db not dumping properly, or at least not restoring |
Previous Message | John R Pierce | 2009-10-16 17:03:43 | Re: Urgent Help required |
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2009-10-16 17:04:42 | Deprecation |
Previous Message | Greg Stark | 2009-10-16 16:45:54 | Re: Reworks for Access Control facilities (r2363) |