On Fri, Oct 16, 2009 at 10:04 AM, decibel wrote:
> 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 appl
On Fri, 2009-10-16 at 12:04 -0500, decibel wrote:
> 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.
If that's the only reason, that seems eas
On Oct 16, 2009, at 10:04 AM, decibel wrote:
Out of curiosity, did you look at doing hints as comments in a query?
I don't think that a contrib module could change the grammar.
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
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
Hi there,
this is an announcement of our new contribution module for PostgreSQL -
Plantuner - enable planner hints
(http://www.sai.msu.su/~megera/wiki/plantuner).
Example:
=# LOAD 'plantuner';
=# create table test(id int);
=# create index id_idx on test(id);
=# create index id_idx2 on test(id
