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, Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>
Subject: Re: Worse perfomance on 8.2.0 than on 7.4.14
Date: 2007-01-01 23:30:27
Message-ID: 21166.1167694227@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

=?iso-8859-1?q?Rolf=20=D8stvik?= <rolfostvik(at)yahoo(dot)no> writes:
> First i have some queries to give you a feel of size
> of datasets and plans and times.

You said earlier that essentially all the rows of step_result_subset
have step_parent = 0 ... is that really true? I can hardly believe
that either 7.4 or 8.2 would use an indexscan for Q-A if so.

I'd be interested to see the results of

prepare foo(int) as select id from step_result_subset sr
where uut_result = $1 and step_parent = 0;
explain analyze execute foo(42);

(use some representative uut_result value instead of 42). If it doesn't
want to use an indexscan for this, disable plan types until it does.
This would perhaps shed some light on why 8.2 doesn't want to use a scan
like that as the inside of a nestloop.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Craig A. James 2007-01-02 01:29:30 glibc double-free error
Previous Message Rolf Østvik 2007-01-01 15:19:05 Re: Worse perfomance on 8.2.0 than on 7.4.14