From: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | subselect and count (DISTINCT expression [ , ... ] ) performances |
Date: | 2008-12-27 11:14:33 |
Message-ID: | 20081227121433.1b40edd2@dawn.webthatworks.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 26 Dec 2008 19:13:48 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The subselect syntax certainly seems like the one most likely to
> work across different SQL implementations. WITH is a pretty
subselects actually works on mysql too but on a 1M table with about
300K unique columns it performs more than 4 times slower than
select (distinct a,b) from table
18sec vs. 4sec
Times were similar for innodb and myisam.
Postgresql needs 17sec with subselect.
I didn't try to see how both db could perform with indexes.
mysql performance is impressive. I thought that most of the time
would be spent on "distinct" where postgresql shouldn't suffer from
its "count" implementation. But well still 300K rows to count on 1M
aren't few.
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-12-27 14:10:17 | Re: Automatic CRL reload |
Previous Message | Craig Ringer | 2008-12-27 09:14:15 | Re: "disappearing" rows in temp table, in recursing trigger |