Re: [GENERAL] Joins and links - Mailing list pgsql-general

From Bruce Momjian
Subject Re: [GENERAL] Joins and links
Date
Msg-id 199907051708.NAA06207@candle.pha.pa.us
Whole thread Raw
In response to Re: [GENERAL] Joins and links  (David Warnock <david@sundayta.co.uk>)
List pgsql-general
> Bruce,
>
> It is amazing when you get responses written this fast (so that the
> reponse arrives before the copy of the message from the list).

Yep.

> > but in fact, heap already does this, doesn't it?
>
> heap? I am not sure what you mean.

Heap is our base table structure.  Records are always inserted on the
end of the heap file.  Vacuum removes old, superceeded rows.

>
> > I guess if you only add occasionally, it is OK.
> > Also, our no-over-write table structure had a tendency to mess up that
> > ordering because updated rows do not go into the same place as the
> > original row.
>
> I have just been thinking a bit more and have realised that the
> multi-generational architecture of 6.5 (which I have used in Interbase)
> means that probably both clustering (in thr dynamic sense) and full
> record number support as request by Leon are impractical.

Yes, would be a big problem.  Most commercial databases have found that
the network data model is impractical in most cases.


--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-general by date:

Previous
From: David Warnock
Date:
Subject: Re: [GENERAL] Joins and links
Next
From: Leon
Date:
Subject: Re[2]: [GENERAL] Joins and links