Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [DOCS] [HACKERS] Please Help: PostgreSQL Query Optimizer
- 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. A." <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: Sun, 11 Dec 2005 15:41:36 -0500
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
- References:
- Please Help: PostgreSQL Query Optimizer
- From: Anjan Kumar. A.
- Re: [HACKERS] Please Help: PostgreSQL Query Optimizer
- From: Josh Berkus
- Please Help: PostgreSQL Query Optimizer
- Prev by Date: Re: [HACKERS] Please Help: PostgreSQL Query Optimizer
- Next by Date: Re: [HACKERS] Please Help: PostgreSQL Query Optimizer
- Previous by thread: Re: [HACKERS] Please Help: PostgreSQL Query Optimizer
- Next by thread: Re: [HACKERS] Please Help: PostgreSQL Query Optimizer
- Indexes: