Re: [HACKERS] Arbitrary tuple size

I knew there had to be a reason that some tests where BLCKSZ/2 and some
BLCKSZ.

Added to TODO:

* Allow index on tuple greater than 1/2 block size

Seems we have to allow columns over 1/2 block size for now. Most people
wouln't index on them.

> > Don't know, maybe.
>
> Actually we have some problems with indices on text
> attributes when the content exceeds HALF of the blocksize:
>
> FATAL 1: btree: failed to add item to the page
>
> It crashes the backend AND seems to corrupt the index! Looks
> to me that at least the btree code needs to be able to store
> at minimum two items into one block and painfully fails if it
> can't.
>
> And just another one:
>
> pgsql=> create table t1 (a int4, b char(4000));
> CREATE
> pgsql=> create index t1_b on t1 (b);
> CREATE
> pgsql=> insert into t1 values (1, 'a');
>
> TRAP: Failed Assertion("!(( itid)->lp_flags & 0x01):",
> File: "nbtinsert.c", Line: 361)
>
> Bruce: One more TODO item!
>
>
> Jan
>
> --
>
> #======================================================================#
> # It's easier to get forgiveness for being wrong than for being right. #
> # Let's break this rule - forgive me. #
> #========================================= wieck(at)debis(dot)com (Jan Wieck) #
>
>
>

--
Bruce Momjian | http://www.op.net/~candle
maillist(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