From: | Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: prefix btree implementation |
Date: | 2005-10-07 03:19:45 |
Message-ID: | Pine.LNX.4.58.0510062315350.26694@eon.cs |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 6 Oct 2005, Jim C. Nasby wrote:
> On Wed, Oct 05, 2005 at 03:40:43PM -0700, Qingqing Zhou wrote:
> > We do the prefix sharing when we build up index only, never on the fly.
>
> So are you saying that inserts of new data wouldn't make any use of
> this? ISTM that greatly reduces the usefulness, though I'm not objecting
> because compression during build is probably better than none at all. Is
> there a technical reason compression can't be used during normal
> operations?
>
Yes, there are. Think if we do it we when build up index, we can choose
the shared prefix optimally w.r.t. maximizing the number of index items on
the page. But on the fly, if we do so, I am afraid this will (1) kill the
performance; (2) introduce more complexities. I don't exclude the
possibility of doing prefix sharing on the fly, but for current stage, I
would like to first come up with a proof-of-concept patch not including
this part.
Regards,
Qingqing
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2005-10-07 03:22:04 | Re: [HACKERS] Patching dblink.c to avoid warning about open transaction |
Previous Message | Bruce Momjian | 2005-10-07 02:43:54 | Re: prefix btree implementation |