pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tomas Vondra <tv@fuzzy.cz>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hash join on int takes 8..114 seconds
Date: Sun, 23 Nov 2008 19:47:15 +0100
Message-ID: <4929A533.5030203@fuzzy.cz> (raw)
In-Reply-To: <AD6DEEFF0CE54A3982082A2CA7C2F722@andrusnotebook>
References: <gg1sv3$27fr$1@news.hub.org>
	<49253FE1.3070706@archonet.com>
	<0205611B528C4C2CBA99AFC64E57D6E8@andrusnotebook>
	<op.ukw669uvcigqcu@soyouz>
	<75A918DFCF25470FAF96B3FE3D25A38B@andrusnotebook>
	<op.ukze24t0cigqcu@soyouz>
	<E3AFB54F617D47F4BE652E85ECC67153@andrusnotebook>
	<op.uk1nbqcgcigqcu@soyouz>
	<AD6DEEFF0CE54A3982082A2CA7C2F722@andrusnotebook>


> Risky to try in prod server. Requires creating  randomly distributed
> product_id testcase to measure
> difference.
> 
> What should I do next?

I guess you have backups - take them, restore the database on a 
different machine (preferably with the same / similar hw config) and 
tune the queries on it.

After restoring all the tables / indexes will be 'clean' (not bloated), 
so you'll see if performing VACUUM FULL / CLUSTER is the right solution 
or if you have to change the application internals.

Sure, the times will be slightly different but the performance problems 
should remain the same.

regards
Tomas



view thread (41+ messages)  latest in thread

Message-ID: <4929A533.5030203@fuzzy.cz>
Permalink:  ../4929A533.5030203@fuzzy.cz/
Also on:    postgresql.org/message-id/4929A533.5030203@fuzzy.cz

 · 

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: tv@fuzzy.cz
  Subject: Re: Hash join on int takes 8..114 seconds
  In-Reply-To: <4929A533.5030203@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