Re: Re: GIST question

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Re: GIST question
Date: 2001-05-15 23:35:09
Message-ID: 200105152335.f4FNZ9S13313@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> I did look at the code inside the tests. The first was to decide if it
> was suppose to look in pg_attribute for the byvalue flag. The last two
> controlled the if gistentryinit() was called. No idea what that is
> because the variable names are single letters. Gistentryinit() is:
>
> #define gistentryinit(e, pr, r, pg, o, b, l)\
> do {(e).pred = pr; (e).rel = r; (e).page = pg; (e).offset = o; (e).bytes = b;
> (e).leafkey = l;} while (0)
>
> I have to say I have no idea how pg_index.indhaskeytype is related to
> gistentryinit().

I figured out part of it. gistentryinit() is related to compressFn and
decompressFn in its calls. It seems they wanted to disable those calls
when haskeytype was false.

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

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2001-05-15 23:38:19 Re: Re: GIST question
Previous Message Bruce Momjian 2001-05-15 22:37:37 Re: Re: GIST question