Skip site navigation (1) Skip section navigation (2)

Re: Worse perfomance on 8.2.0 than on 7.4.14

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rolf Østvik <rolfostvik(at)yahoo(dot)no>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Worse perfomance on 8.2.0 than on 7.4.14
Date: 2006-12-31 17:11:28
Message-ID: 4049.1167585088@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Rolf =?iso-8859-1?q?=D8stvik?= <rolfostvik(at)yahoo(dot)no> writes:
> I have a simple query which uses 32ms on 7.4.14 and 1015ms on 8.2.0.

There's something awfully strange about that 8.2 plan --- if it knew
that it'd have to scan all of uut_result_subset (which it should have
known, if the stats were up-to-date), why did it use an indexscan
rather than a seqscan?  Are you sure you haven't tweaked any parameters
you didn't tell us about, such as setting enable_seqscan = off?

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Rolf ØstvikDate: 2007-01-01 15:04:10
Subject: Re: Worse perfomance on 8.2.0 than on 7.4.14
Previous:From: Dave CramerDate: 2006-12-31 16:26:53
Subject: Re: Worse perfomance on 8.2.0 than on 7.4.14

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group