Re[2]: [GENERAL] Joins and links

From: Leon <leon(at)udmnet(dot)ru>
To: Clark Evans <clark(dot)evans(at)manhattanproject(dot)com>, David Warnock <david(at)sundayta(dot)co(dot)uk>, pgsql-general <pgsql-general(at)postgreSQL(dot)org>
Subject: Re[2]: [GENERAL] Joins and links
Date: 1999-07-05 18:57:25
Message-ID: 2998.990705@udmnet.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Hello Clark,

Monday, July 05, 1999 you wrote:

C> In my understanding, pointer based approaches like you
C> are recommending have been implemented in several prototype
C> objected oriented databases. They have been shown to be
C> orders of magnitude slower than set oriented techniques,thus
C> many OO databases are implemented as wrappers over
C> relational systems!

I can't guess where you got such information. Contrarily,
I know at least one (commercial) network database server which
orders of magnitude faster than ANY SQL server. It simply no
match to them. That experience is exactly what made me write
to Postgres mailing list. As I wrote (maybe to hackers' list)
pointer lookup takes ideally three CPU commands - read,
multiply, lookup, whereas index scan takes dozens of them and
puts a strain on optimizer's intellectual abilities, and
as we have seen it can hardly choose the optimum way of
performing a join. In pointer-field case optimizer can be quite
dumb, because there is only one way to perform a query.

Best regards, Leon

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 1999-07-05 19:10:34 Re: Re[2]: [GENERAL] Joins and links
Previous Message Kane Tao 1999-07-05 18:37:27 Fw: Re[2]: [GENERAL] Joins and links

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-07-05 19:02:25 Re: Re[2]: [HACKERS] Fwd: Joins and links
Previous Message Clark Evans 1999-07-05 18:36:20 Re: [GENERAL] Joins and links