On Mon, Jun 25, 2012 at 4:09 PM, Tom Lane wrote:
> The short answer though is that this is probably coming from CPU cost
> components not disk-access components.
Yes of course they are cpu costs, but I'm not able to understand which
ones. Is there a way to make PostgreSQL to log the values of the
Luca Ferrari writes:
> Now, what is the .35 in the cost of the bitmap index scan nodes?
If you're going to get picky about second-order cost components,
it's time to start reading the source code:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/optimizer/path/costsize.c;h
Hi all,
imagine the following simple situation:
# CREATE TABLE test( pk serial not null, description text, primary key(pk));
# INSERT INTO test(pk) VALUES(generate_series(1,100 ) );
# VACUUM FULL ANALYZE test;
# EXPLAIN SELECT * FROM test WHERE pk = 1 OR pk = 100;
