pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Tyrrill, Ed <tyrrill_ed@emc.com>
Cc: pgsql-performance@postgresql.org
Subject: Re:
Date: Mon, 25 Jun 2007 17:56:54 -0400
Message-ID: <20070625215654.GF7531@tamriel.snowman.net> (raw)
In-Reply-To: <A23190A408F7094FAF446C1538222F76041E1C28@avaexch01.avamar.com>
References: <A23190A408F7094FAF446C1538222F76041E1C28@avaexch01.avamar.com>

* Tyrrill, Ed (tyrrill_ed@emc.com) wrote:
> Based on all this we will be going with 8.2.4.1, but it seems like
> currently the query planner isn't choosing the best plan for this case.

Was the 'work_mem' set to the same thing on all these runs?  Also, you
might try increasing the 'work_mem' under 8.2.4, at least for this query
(you can set it by just doing: set work_mem = '2GB'; or similar in psql,
or you can change the default in postgresql.conf).

The big thing of note, it seems, is that you've got enough memory and
it's coming out faster when doing a hash-join vs. a sort + merge-join.
Could likely be because it doesn't think there's enough work memory
available for the hash, which might change based on the values it gets
from the statistics on how frequently something shows up, etc.

	Enjoy,

		Stephen

Attachments:

  signature.asc (application/pgp-signature, 188B) download

view thread (9+ messages)  latest in thread

Message-ID: <20070625215654.GF7531@tamriel.snowman.net>
Permalink:  ../20070625215654.GF7531@tamriel.snowman.net/
Also on:    postgresql.org/message-id/20070625215654.GF7531@tamriel.snowman.net

 · 

reply

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: sfrost@snowman.net, tyrrill_ed@emc.com
  Subject: Re:
  In-Reply-To: <20070625215654.GF7531@tamriel.snowman.net>

* 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