From: | Bob Devine <devine(at)cs(dot)utah(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Fwd: Joins and links |
Date: | 1999-07-07 19:20:51 |
Message-ID: | 3783A893.5DC77215@cs.utah.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Leon <leon(at)udmnet(dot)ru> wrote:
> Earlier I proposed that links should be of type similar to tid,
> so inserts should be fed with values of tid. But this requires
> intermediate step, so there can be a function which takes primary
> key and returns tid, or as you say a function
> last_touched('other_table_name') - this seems the best choice.
Beware of adding special purpose hard-links as a way to
skip the run-time value comparisons. A link looks attractive
but it really only works for one-to-one relationships
(any multi-way relationships would require a list of links
to follow) and a link has all of the overhead that a
foreign key requires.
As somone who has developed several commercial dbms systems,
I would discourage doing a special "link" type. There are
other ways to gain performance -- de-normalize your tables
if you are doing mainly reads; carefully check your storage
layout; and, of course, buy more RAM ;-)
--
Bob Devine devine(at)cs(dot)utah(dot)edu
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 1999-07-07 19:53:13 | Re: [HACKERS] Re: Postgresql 6.5-1 rpms on RedHat 6.0 |
Previous Message | Bruce Momjian | 1999-07-07 19:03:58 | Re: [HACKERS] 6.5 cvs: views doesn't survives after pg_dump (fwd) |