| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Tobias Brox <tobias(at)nordicbet(dot)com> |
| Cc: | Jeffrey Tenny <jeffrey(dot)tenny(at)comcast(dot)net>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Need help to decide Mysql vs Postgres |
| Date: | 2005-06-06 18:33:40 |
| Message-ID: | 20050606183340.GA38889@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Jun 06, 2005 at 08:25:08PM +0300, Tobias Brox wrote:
> [Jeffrey Tenny - Mon at 11:51:22AM -0400]
> > There are some pitfalls to pgsql though, especially for existing SQL
> > code using MAX and some other things which can really be blindsided
> > (performance-wise) by pgsql if you don't use the workarounds.
>
> Yes, I discovered that - "select max(num_attr)" does a full table scan even
> if the figure can be found easily through an index.
PostgreSQL 8.1 will be able to use indexes for MIN and MAX.
http://archives.postgresql.org/pgsql-committers/2005-04/msg00163.php
http://archives.postgresql.org/pgsql-committers/2005-04/msg00168.php
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2005-06-06 18:55:23 | Re: Need help to decide Mysql vs Postgres |
| Previous Message | Vivek Khera | 2005-06-06 18:32:14 | Re: Postgresql on an AMD64 machine |