From: | ncm(at)zembu(dot)com (Nathan Myers) |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: AW: pg_index.indislossy |
Date: | 2001-07-10 19:26:22 |
Message-ID: | 20010710122622.F23310@store.zembu.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 10, 2001 at 01:36:33PM -0400, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > But why is this called lossy? Shouldn't it be called "exceedy"?
>
> Good point ;-). "lossy" does sound like the index might "lose" tuples,
> which is exactly what it's not allowed to do; it must find all the
> tuples that match the query.
>
> The terminology is correct by analogy to "lossy compression" --- the
> index loses information, in the sense that its result isn't quite the
> result you wanted. But I can see where it'd confuse the unwary.
> Perhaps we should consult the literature and see if there is another
> term for this concept.
How about "hinty"? :-)
Seriously, "indislossy" is a singularly poor name for a predicate.
Also, are we so poor that we can't afford whole words, or even word
breaks? I propose "index_is_hint".
Actually, is the "ind[ex]" part even necessary?
How about "must_check_heap"?
Nathan Myers
ncm(at)zembu(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Shraibman | 2001-07-10 19:33:29 | Re: Re: Backups WAS: 2 gig file size limit |
Previous Message | Alex Pilosov | 2001-07-10 18:27:20 | selecting from cursor/function |