| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "Anjan Kumar(dot) A(dot)" <anjankumar(at)cse(dot)iitb(dot)ac(dot)in>, pgsql-chat(at)postgresql(dot)org, pgsql-benchmarks(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: [DOCS] [HACKERS] Please Help: PostgreSQL Query Optimizer |
| Date: | 2005-12-11 20:41:36 |
| Message-ID: | 18706.1134333696@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-benchmarks pgsql-chat pgsql-docs pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> I don't see why you're increasing the various cpu_* costs.
You missed the point Josh --- these numbers are relative to the cost of
a page fetch, so if page fetch is measured in microseconds instead of
milliseconds, then you *do* want to bump the CPU costs up.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anjan Kumar. A. | 2005-12-11 22:06:01 | Re: [HACKERS] Please Help: PostgreSQL Query Optimizer |
| Previous Message | Josh Berkus | 2005-12-11 19:26:18 | Re: [HACKERS] Please Help: PostgreSQL Query Optimizer |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anjan Kumar. A. | 2005-12-11 22:06:01 | Re: [HACKERS] Please Help: PostgreSQL Query Optimizer |
| Previous Message | Josh Berkus | 2005-12-11 19:26:18 | Re: [HACKERS] Please Help: PostgreSQL Query Optimizer |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anjan Kumar. A. | 2005-12-11 22:06:01 | Re: [HACKERS] Please Help: PostgreSQL Query Optimizer |
| Previous Message | Josh Berkus | 2005-12-11 19:26:18 | Re: [HACKERS] Please Help: PostgreSQL Query Optimizer |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-12-11 21:26:22 | Re: Reducing contention for the LockMgrLock |
| Previous Message | Josh Berkus | 2005-12-11 19:26:18 | Re: [HACKERS] Please Help: PostgreSQL Query Optimizer |