From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Barry Lind <barry(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Suggestion for optimization |
Date: | 2002-04-08 03:23:03 |
Message-ID: | 200204080323.g383N3V11695@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher Kings-Lynne wrote:
> > > Af far as I know Oracle doesn't have any short cut (along the lines of
> > > what is being discussed in this thread) for this operation. However
> > > Oracle is more efficient in providing the answer than postgres
> > currently
> > > is. While postgres needs to perform a full scan on the table, Oracle
> > > will only need to perform a full index scan on the primary key if one
> > > exists. Since the index will likely have much less data than the full
> >
> > Under Postgres, a full index scan is generally more expensive than a full
> > table scan since indices, particularly btree, carry a large amount of meta
> > data and theefore consume more pages.
>
> Don't forget that Postgres also doesn't store tids in the index, so must
I assume you mean xid here. tids are in the index or there would be no
way to find the heap row. :-)
> always check with the main table that a row is visible in current
> transaction.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-08 03:33:30 | Re: RFC: Restructuring pg_aggregate |
Previous Message | Bruce Momjian | 2002-04-08 03:22:03 | Re: timeout implementation issues |