pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vitaly Belman <vitalib@012.net.il>
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Rod Taylor <pg@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Simply join in PostrgeSQL takes too long
Date: Fri, 30 Apr 2004 00:09:36 +0300
Message-ID: <147254626500.20040430000936@012.net.il> (raw)
In-Reply-To: <tlpu80tqhmnpc2sl63boejki6o4vbn1p3q@email.aon.at>
References: <282909734.20040428002740@012.net.il>
	<1083103293.30065.100.camel@jester>
	<tlpu80tqhmnpc2sl63boejki6o4vbn1p3q@email.aon.at>

Hello Manfred,

I thank everyone for helping me on this - So many tips.

I am in the middle of going through them all, till now disabling the
enable_mergejoin really helped.

Also, I agree that the design might be flawed (I could use triggers
and stuff like that) but for now I am just comparing how my project
will run on PostgreSQL (Considering migration from MySQL).

I'll be reporting back on how the other stuff helped.

Regards,
 Vitaly Belman
 
 ICQ: 1912453
 AIM: VitalyB1984
 MSN: tmdagent@hotmail.com
 Yahoo!: VitalyBe

Wednesday, April 28, 2004, 11:24:41 AM, you wrote:

MK> On Tue, 27 Apr 2004 18:01:34 -0400, Rod Taylor <pg@rbt.ca> wrote:
>>On Tue, 2004-04-27 at 17:27, Vitaly Belman wrote:
>>> Hello pgsql-performance,
>>> 
>>>   I discussed the whole subject for some time in DevShed and didn't
>>>   achieve much (as for results). I wonder if any of you guys can help
>>>   out:
>>> 
>>>   http://forums.devshed.com/t136202/s.html

>>The point is that a book cannot be of a certain genre more than once.

MK> Rod, he has a hierarchy of genres.  Genre 1 has 6379 child genres and a
MK> book can be in more than one of these.

MK> Vitaly, though LIMIT makes this look like a small query, DISTINCT
MK> requires the whole result set to be retrieved.  0.7 seconds doesn't look
MK> so bad for several thousand rows.  Did you try with other genre_ids?

MK> Maybe a merge join is not the best choice.  Set enable_mergejoin to
MK> false and see whether you get a (hopefully faster) hash join, assuming
MK> that sort_mem is large enough to keep the hash table in memory.

MK> If you send me your table contents I'll try it on Linux.

MK> Servus
MK>  Manfred




view thread (12+ messages)  latest in thread

Message-ID: <147254626500.20040430000936@012.net.il>
Permalink:  ../147254626500.20040430000936@012.net.il/
Also on:    postgresql.org/message-id/147254626500.20040430000936@012.net.il

 · 

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: vitalib@012.net.il, mkoi-pg@aon.at, pg@rbt.ca
  Subject: Re: Simply join in PostrgeSQL takes too long
  In-Reply-To: <147254626500.20040430000936@012.net.il>

* 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