Re: Weird performance drop after VACUUM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Weird performance drop after VACUUM
Date: 2005-08-27 15:05:01
Message-ID: 1404.1125155101@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Steinar H. Gunderson" <sgunderson(at)bigfoot(dot)com> writes:
> On Fri, Aug 26, 2005 at 07:31:51PM -0400, Tom Lane wrote:
>> Or you could just play with the order of the filter conditions ... for
>> example, the date condition at the end is probably far cheaper to test
>> than the text comparisons, so if that's fairly selective it'd be worth
>> putting it first.

> That's an interesting approach -- could the planner do such things itself?

It could, but it doesn't really have enough information. We don't
currently have any model that some operators are more expensive than
others. IIRC the only sort of reordering the current code will do
in a filter condition list is to push clauses involving sub-SELECTs
to the end.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Ron 2005-08-27 15:07:37 Re: Inefficient queryplan for query with
Previous Message Tom Lane 2005-08-27 14:27:01 Re: Inefficient queryplan for query with intersectable