| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Craig James <craig_james(at)emolecules(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: count * performance issue |
| Date: | 2008-03-06 15:33:25 |
| Message-ID: | 200803061533.m26FXPe19222@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Craig James wrote:
> This is a real problem. Countless people (including me) have
> spent significant effort rewriting applications because of this
> performance flaw in Postgres. Over and over, the response is,
> "You don't really need to do that ... change your application."
> Well, sure, it's always possible to change the application, but
> that misses the point. To most of us users, count() seems like
> it should be a trivial operation. On other relational database
> systems, it is a trivial operation.
>
> This is really a significant flaw on an otherwise excellent
> relational database system.
Have you read the TODO items related to this?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steinar H. Gunderson | 2008-03-06 15:36:39 | Re: count * performance issue |
| Previous Message | Craig James | 2008-03-06 15:28:50 | Re: count * performance issue |