| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Firebird 1.0 released |
| Date: | 2002-04-16 05:11:19 |
| Message-ID: | 9499.1018933879@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> The Firebird guys have gotten around to releasing 1.0. If you read this
> front page spiel, you'll notice that they use MVCC, but with an overwriting
> storage manager.
Yup. I've had a couple of long chats with Ann Harrison at the recent
"OSDB summit" meetings. I think we each came away enlightened about the
other implementation, but not in any large hurry to change our own.
I did steal at least one idea from her, though. (rummages in CVS logs)
ah, here's a hit:
2001-09-29 19:49 tgl
* src/backend/access/nbtree/nbtinsert.c: Tweak btree page split
logic so that when splitting a page that is rightmost on its tree
level, we split 2/3 to the left and 1/3 to the new right page,
rather than the even split we use elsewhere. The idea is that when
faced with a steadily increasing series of inserted keys (such as
sequence or timestamp values), we'll end up with a btree that's
about 2/3ds full not 1/2 full, which is much closer to the desired
steady-state load for a btree. Per suggestion from Ann Harrison of
IBPhoenix.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manuel Sugawara | 2002-04-16 05:11:50 | Re: regexp character class locale awareness patch |
| Previous Message | Bruce Momjian | 2002-04-16 05:06:50 | Re: [PATCHES] [SQL] 16 parameter limit |