Hi Heikki, Pgsql-Hackers,

Sometime back you have started with "Separate Heap Fetch from Index Scan" which 
was planned to support partial index only scans. Are you still working on it or 
do you know someone still working on it?

We did some development with Gokul's Index Only Patch and have got good 
performance numbers which are as follows:

Test table constitutes 0.5 billion records with thick index on (id,aid) on 
three machines {pg_normal , pg_enhanced( PGSQL with thick index feature ), 
Oracle} each having 16 Gb Ram. Disk I/O obtained using sar.

testdb=# \d test
           Table "public.test"
  Column   |       Type       | Modifiers
-----------+------------------+-----------
 id        | integer          |
 startdate | date             |
 enddate   | date             |
 charge    | double precision |
 firstname | text             |
 lastname  | text             |
 aid       | double precision |
 bid       | double precision |
Indexes:
    "taid" THICK btree (id, aid) CLUSTER

Index size
On oracle               15.20 Gb
On Pg-normal    14.73 Gb
Pg_enhanced     23.17 Gb (16bytes*0.5billion = ~7.6 GB)

PFA excel sheet for details. In general we saw fair amount of performance 
improvement, but one thing that surprises us is that after around 20% tuples 
updated we found oracle taking more time.

Regards,
Shrish Purohit |Senior Software Engineer|Persistent Systems
shrish_puro...@persistent.co.in |Cell:+91-9850-959-940|Tel:+91(20)302-34493
Innovation in software product design, development and delivery- 
www.persistentsys.com


DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

Attachment: Thick_index_perf_numbers.xlsx
Description: Thick_index_perf_numbers.xlsx

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to