| From: | Itai Zukerman <zukerman(at)math-hat(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | GiST: spl_rattr in gistSplit() |
| Date: | 2003-03-02 12:52:03 |
| Message-ID: | 87znoeylqk.fsf@matt.w80.math-hat.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[3rd day of trying to track down a SEGV]
In gistSplit() I see:
newtup[0] = gistFormTuple(giststate, r, v.spl_rattr, v.spl_rattrsize, v.spl_risnull);
but v.spl_rattrsize hasn't been initialized:
(gdb) p v.spl_rattrsize[0]
$136 = -1073749368
Is this going to be a problem? Eventually we get a GISTENTRY with bad
bytes in gistFormTuple(), but maybe it's never used?
(gdb) p centry[0]
$138 = {key = 137280264, rel = 0x0, page = 0x0, offset = 0, bytes = -1073749368, leafkey = 0 '\0'}
--
Itai Zukerman <http://www.math-hat.com/~zukerman/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Itai Zukerman | 2003-03-02 13:13:16 | GiST: Bad newtup On Exit From gistSplit() ? |
| Previous Message | Hans-Jürgen Schönig | 2003-03-02 08:11:40 | Re: System Tables and Triggers |