| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com> |
| Cc: | Guy Rouillier <guyr-ml1(at)burntmail(dot)com>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: High update activity, PostgreSQL vs BigDBMS |
| Date: | 2007-01-08 18:09:16 |
| Message-ID: | 200701081809.l08I9G024520@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Craig A. James wrote:
> Postgres functions like count() and max() are "plug ins" which has huge
> architectural advantages. But in pre-8.1 releases, there was a big
> speed penalty for this: functions like count() were very, very slow,
> requiring a full table scan. I think this is vastly improved from 8.0x
> to 8.1 and forward; others might be able to comment whether count() is
> now as fast in Postgres as Oracle. The "idiom" to replace count() was
^^^^^^
BigDBMS == Oracle. ;-)
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Dutcher | 2007-01-08 18:59:14 | Re: Slow Query on Postgres 8.2 |
| Previous Message | Luke Lonergan | 2007-01-08 15:39:21 | Re: table partioning performance |