pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: Sebastian Hennebrueder <usenet@laliluna.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL vs MySQL, and FreeBSD
Date: Fri, 16 Nov 2007 17:43:05 +0800
Message-ID: <1195206185.29253.56.camel@neuromancer.home.net> (raw)
In-Reply-To: <47347F9F.1070309@laliluna.de>
References: <47344D43.5090506@geri.cc.fer.hr>
	<47347F9F.1070309@laliluna.de>


On Fri, 2007-11-09 at 16:41 +0100, Sebastian Hennebrueder wrote:

> If the queries are complex, this is understable. I had a performance
> review of a Hibernate project (Java Object Relation Mapping) using
> MySQL. ORM produces easily "complex" queries with joins and subqueries.
> MySQL uses nested loops for subqueries which lead to performance issues
> with growing database size.

Even for Postgresql, nested loops are still evil and hampers
performance.






view thread (20+ messages)  latest in thread

Message-ID: <1195206185.29253.56.camel@neuromancer.home.net>
Permalink:  ../1195206185.29253.56.camel@neuromancer.home.net/
Also on:    postgresql.org/message-id/1195206185.29253.56.camel@neuromancer.home.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: Ow.Mun.Heng@wdc.com, usenet@laliluna.de
  Subject: Re: PostgreSQL vs MySQL, and FreeBSD
  In-Reply-To: <1195206185.29253.56.camel@neuromancer.home.net>
  References: <47344D43.5090506@geri.cc.fer.hr> <47347F9F.1070309@laliluna.de> <1195206185.29253.56.camel@neuromancer.home.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