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

Re: Performance issues migrating from 743 to 826

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: mlunnon(at)rwa-net(dot)co(dot)uk
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Performance issues migrating from 743 to 826
Date: 2008-01-28 15:39:54
Message-ID: dcc563d10801280739h7b21720eqd54658e71cd5f115@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
Whatever email agent you're using seems to be quoting in a way that
doesn't get along well with gmail, so I'm just gonna chop most of it
rather than have it quoted confusingly...  Heck, I woulda chopped a
lot anyway to keep it small. :)

On Jan 28, 2008 9:27 AM, Matthew Lunnon <mlunnon(at)rwa-net(dot)co(dot)uk> wrote:
>
>  Scott Marlowe wrote:
>  On Jan 28, 2008 5:41 AM, Matthew Lunnon <mlunnon(at)rwa-net(dot)co(dot)uk> wrote:
> default_statistics_target = 1000
> >  That's very high for the default. Planning times will be increased
> > noticeably
>
>  I had originally left the default_statistics_target at its default and then
> increased it to 100, but this did not seem to make much difference.  I will
> reduce this down to something more normal again.

You do know that if you create a column when the default is 10, then
increase the default, it won't change the column's stats target,
right?  So, assuming the table was first created, then you changed the
default, you'll now need to do:

alter table xyz alter column abc set statistics 100;
analyze xyz;

for it to make any difference.

>  The queries were on exactly the same data. My interpretation of what is
> going on here is that 8.2.6 seems to be leaving the filtering of market_id
> to the very last point, which is why it ends up with 189 rows at this point
> instead of the 2 that 743 has. 743 seems to do that filtering much earlier
> and so reduce the number of rows at a much earlier point in the execution of
> the query. I guess that this is something to do with the planner which is
> why I tried increasing the default_statistics_target.

Ahh, I'm guessing it's something that your 7.4 database CAN use an
index on and your 8.2 data base can't use an index on.  Like text in a
non-C locale.  Or something...  Table def?

In response to

Responses

pgsql-performance by date

Next:From: Matthew LunnonDate: 2008-01-28 15:49:25
Subject: Re: Performance issues migrating from 743 to 826
Previous:From: Matthew LunnonDate: 2008-01-28 15:27:50
Subject: Re: Performance issues migrating from 743 to 826

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