Re: Rewriting using rules for performance

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Matthew Wakeling <matthew(at)flymine(dot)org>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Rewriting using rules for performance
Date: 2009-04-03 13:46:32
Message-ID: 603c8f070904030646u654f4cbbh92e7b42180fa04d0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Apr 3, 2009 at 9:17 AM, Matthew Wakeling <matthew(at)flymine(dot)org> wrote:
> So, I have a view. The query that the view uses can be written two different
> ways, to use two different indexes. Then I use the view in another query,
> under some circumstances the first way will be quick, and under other
> circumstances the second way will be quick.
>
> What I want to know is, can I create a view that has both queries, and
> allows the planner to choose which one to use? The documentation seems to
> say so in http://www.postgresql.org/docs/8.3/interactive/querytree.html (the
> rule system "creates zero or more query trees as result"), but doesn't say
> how one would do it.

I think this would be clearer if you gave an actual example of what
you're trying to accomplish, but the short answer is "no". The rule
system lets you create multiple query trees to perform multiple
actions (for example, when an INSERT command is issued, do the
original insert plus also an update) and it implements views. But
it's independent of query planning.

On the other hand, the query planner should be figuring out which
index to use without any help from you. If it's not, something is
wrong.

...Robert

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Robert Haas 2009-04-03 13:47:31 Re: plpgsql arrays
Previous Message Matthew Wakeling 2009-04-03 13:32:54 plpgsql arrays