Re: SQL performance issue with PostgreSQL compared to MySQL

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff Self <jself(at)nngov(dot)com>, pgsql-sql(at)postgresql(dot)org
Subject: Re: SQL performance issue with PostgreSQL compared to MySQL
Date: 2002-06-19 16:43:04
Message-ID: 200206191643.g5JGh4D10793@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Tom Lane wrote:
> Jeff Self <jself(at)nngov(dot)com> writes:
> > if it's too OT, let me know, and I'll stop. The query "SELECT authuser,
> > SUM(bytes) AS traffic FROM logfile GROUP BY authuser ORDER BY traffic"
> > [is slow]
>
> What datatype are the columns used in the query? And what PG version
> are we talking about?

My guess is that is the lack of hashing for GROUP BY aggregating that is
killing us. TODO has:

* Add hash for evaluating GROUP BY aggregates

and I specifically remember MySQL has such a hash. The big question is
how many unique values are there in the group. If it is large, the
missing hashing could be the problem.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Michael Agbaglo 2002-06-19 18:03:28 syntax for access an alias in the where clause ?
Previous Message Steve Wampler 2002-06-19 16:02:03 Tagging rows into collections?