| From: | Micah Yoder <yodermk(at)home(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Storing a tree |
| Date: | 2001-11-10 19:28:07 |
| Message-ID: | 20011110222800.BGNE3462.femail46.sdc1.sfba.home.com@there |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
On Saturday 10 November 2001 10:08 am, Antonio Fiol Bonnín wrote:
> If you consider the approach using multiple trees, it may have quite a good
> performance even for something like a threaded message board, if you think
> of each thread as a different tree. Then trees are not enormous, and so
> updates would not be so slow.
>
> Performance will be poor, however, when updating very large trees.
Ok, I guess you're right. I was thinking all messages in a large database
would be in the same tree. Of course, they would all be in the same table,
but it would just need a 'toplevel' field for the root message ID for the
thread (which may itself need to be in another table), and with an index on
that field it shouldn't be too bad.
--
Like to travel? http://TravTalk.org
Micah Yoder Internet Development http://yoderdev.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Ryan | 2001-11-11 03:36:14 | Re: OT?: PGReplication project dead? |
| Previous Message | Jean-Michel POURE | 2001-11-10 17:15:19 | Re: Storing a tree |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Jarman | 2001-11-11 07:02:40 | SQLException: ERROR: oidin: when loading GIF file |
| Previous Message | Jean-Michel POURE | 2001-11-10 17:15:19 | Re: Storing a tree |