Since sequential access is not significantly faster than random access in a
MMDB, random_page_cost will be approximately same as sequential page fetch cost.
As every thing is present in Main Memory, we need to give approximately same
cost to read/write to Main Memory and CPU Related operation
Josh Berkus 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.
Anjan,
> In our case we are reading pages from Main Memory File System, but not from
> Disk. Will it be sufficient, if we change the default values of above
> paramters in "src/include/optimizer/cost.h and
> src/backend/utils/misc/postgresql.conf.sample" as follows:
>
> random_page_cost
I'm working on a project, whose implementation deals with PostgreSQL. A brief
description of the project is given below.
Project Description:
In Main Memory DataBase(MMDB) entire database on the disk is loaded on to
the main memory during initial startup of the sys
