From: Michael Fuhr <mike@fuhr.org>
To: Tobias Brox <tobias@nordicbet.com>
Cc: Jeffrey Tenny <jeffrey.tenny@comcast.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Need help to decide Mysql vs Postgres
Date: Mon, 6 Jun 2005 12:33:40 -0600
Message-ID: <20050606183340.GA38889@winnie.fuhr.org> (raw)
In-Reply-To: <20050606172508.GB8451@tobias.nordicbet.com>
References: <42A470FA.1080001@comcast.net>
<20050606172508.GB8451@tobias.nordicbet.com>
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.phphttp://archives.postgresql.org/pgsql-committers/2005-04/msg00168.php
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mike@fuhr.org, tobias@nordicbet.com, jeffrey.tenny@comcast.net
Subject: Re: Need help to decide Mysql vs Postgres
In-Reply-To: <20050606183340.GA38889@winnie.fuhr.org>
* 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