pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Rod Taylor <rbt@rbt.ca>
Cc: Oleg Lebedev <oleg.lebedev@waterford.org>
Cc: Jeff <threshar@torgo.978.org>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Tuning/performance issue...
Date: Fri, 3 Oct 2003 22:38:17 -0400 (EDT)
Message-ID: <200310040238.h942cHX12107@candle.pha.pa.us> (raw)
In-Reply-To: <1065234119.23288.13.camel@jester>

Rod Taylor wrote:
-- Start of PGP signed section.
> On Fri, 2003-10-03 at 21:39, Bruce Momjian wrote:
> > I have updated the FAQ to be:
> > 
> >       In comparison to MySQL or leaner database systems, we are
> >       faster for multiple users, complex queries, and a read/write query
> >       load.  MySQL is faster for SELECT queries done by a few users. 
> > 
> > Is this accurate?  It seems so.
> 
> May wish to say ... for simple SELECT queries ...

Updated.

> Several left outer joins, subselects and a large number of joins are
> regularly performed faster in PostgreSQL due to a more mature optimizer.
> 
> But MySQL can pump out SELECT * FROM table WHERE key = value; queries in
> a hurry.
> 
> 
> I've often wondered if they win on those because they have a lighter
> weight parser / optimizer with less "lets try simplifying this query"

I think that is part of it.

> steps or if the MYISAM storage mechanism is simply quicker at pulling
> data off the disk.

And their heap is indexed by myisam, right. I know with Ingres that Isam
was usually faster than btree because you didn't have all those leaves
to traverse to get to the data.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (16+ messages)  latest in thread

Message-ID: <200310040238.h942cHX12107@candle.pha.pa.us>
Permalink:  ../200310040238.h942cHX12107@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200310040238.h942cHX12107@candle.pha.pa.us

 · 

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: pgman@candle.pha.pa.us, rbt@rbt.ca, oleg.lebedev@waterford.org, threshar@torgo.978.org
  Subject: Re: Tuning/performance issue...
  In-Reply-To: <200310040238.h942cHX12107@candle.pha.pa.us>
  References: <1065234119.23288.13.camel@jester> <200310040238.h942cHX12107@candle.pha.pa.us>

* 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