| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Sandeep Srinivasa <sss(at)clearsenses(dot)com> |
| Cc: | Ma Sivakumar <masivakumar(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: MySQL versus Postgres |
| Date: | 2010-08-12 05:41:06 |
| Message-ID: | 4C638972.20608@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sandeep Srinivasa wrote:
> Maybe a tabular form would be nice - "work_mem" under...
The problem with work_mem in particular is that the useful range depends
quite a bit on how complicated you expect the average query running to
be. pgtune tries to model this using an input of what type of
application you're running; presuming that a data warehouse application
is far more likely to sort/hash a lot of data in one query than a web
application for example. But even that relatively simple idea has
proven to be confusing to a lot of people, based on the feedback I've
gotten.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ma Sivakumar | 2010-08-12 06:29:13 | Re: MySQL versus Postgres |
| Previous Message | John R Pierce | 2010-08-12 05:39:01 | Re: deadlock |