Skip site navigation (1) Skip section navigation (2)

Re: spgist: palloc() negative size with smaller BLCKSZ

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: spgist: palloc() negative size with smaller BLCKSZ
Date: 2012-06-26 02:57:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Josh Kupershmidt <schmiddy(at)gmail(dot)com> writes:
> I noticed that configuring Postgres with a BLCKSZ smaller than default
> was causing 'make check' give an interesting error on git head.
> [ spgist regression test fails ]


> I'm not sure what'd be the right
> way to fix this after reading the comment above
> SPGIST_MAX_PREFIX_LENGTH, but thought I'd share.

I don't see any way for spgtextproc to support BLCKSZ of 4K or less
without some compromise of functionality.  We have a number of possible
ways we could compromise:

1. Just fail outright for small BLCKSZ.  Probably not very nice
considering the spgist regression test would then fall over.

2. Set SPGIST_MAX_PREFIX_LENGTH to something reasonable (maybe about
50 bytes or so) and just accept the possibility that it will fail if
an internal node gets too large due to too many distinct node labels.
This isn't really desirable either, but I suspect the probability of
failure in practice is pretty low, so it might be the right level of
effort considering use of non-8K BLCKSZ in the field is negligible.

3. Do something to reduce the number of node labels that are possible
when BLCKSZ is too small; for instance we could mask off the high order
bit so as to merge values that have the same next byte mod 128.  The
trouble with this is that spgtextproc currently uses the node label
literally as the next byte when reconstructing strings.  We'd have to
not use the node label for that, which would bloat entries slightly,
and perhaps worse would result in a significant difference in index
logic for large and small index pages.  I don't think I really want to
go there, especially not in the absence of a buildfarm machine testing
the small-page case.

I'm kind of leaning to #2, but anybody have another idea?

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Dave PageDate: 2012-06-26 10:26:54
Subject: Re: BUG #6705: 32 bit
Previous:From: Josh KupershmidtDate: 2012-06-26 02:09:54
Subject: spgist: palloc() negative size with smaller BLCKSZ

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group