From: Tomas Vondra <tv@fuzzy.cz>
To: pgsql-performance@postgresql.org
Subject: Re: help speeding up a query in postgres 8.4.5
Date: Wed, 06 Apr 2011 20:13:19 +0200
Message-ID: <4D9CAD3F.8040606@fuzzy.cz> (raw)
In-Reply-To: <4D9C4182020000250003C3AB@gw.wicourts.gov>
References: <4D9B6CBA.2050609@nasa.gov>
<BANLkTimiH7Gf-PH5g7pTk57+Cjvn-rss3w@mail.gmail.com>
<4D9C6BA6.4070305@nasa.gov>
<4D9C4182020000250003C3AB@gw.wicourts.gov>
Dne 6.4.2011 17:33, Kevin Grittner napsal(a):
> "Maria L. Wilson" <Maria.L.Wilson-1@nasa.gov> wrote:
>
>> Autovacuum is not running - but regular vacuums are being done
>> twice daily.
>
> Is the ANALYZE keyword used on those VACUUM runs? What version of
> PostgreSQL is this. If it's enough to need fsm settings, do you run
> with the VERBOSE option and check the end of the output to make sure
> they are set high enough?
Why do you think the problem is related to stale stats? It seems to me
fairly accurate - see the explain analyze in the first post). All the
nodes are less than 1% off (which is great), except for the last hash
join that returns 336949 rows instead of 924675 expected rows.
Maybe I'm missing something, but the stats seem to be quite accurate and
there is just very little dead tuples I guess.
regards
Tomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tv@fuzzy.cz
Subject: Re: help speeding up a query in postgres 8.4.5
In-Reply-To: <4D9CAD3F.8040606@fuzzy.cz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox