Re: [HACKERS] Arbitrary tuple size
От | wieck@debis.com (Jan Wieck) |
---|---|
Тема | Re: [HACKERS] Arbitrary tuple size |
Дата | |
Msg-id | m112JQL-0003kiC@orion.SAPserv.Hamburg.dsh.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] Arbitrary tuple size (wieck@debis.com (Jan Wieck)) |
Ответы |
Re: [HACKERS] Arbitrary tuple size
|
Список | pgsql-hackers |
I wrote: > > Tom Lane wrote: > > > > Aren't index tuples still tuples? Can't they be split just like > > regular tuples? > > 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@debis.com (Jan Wieck) #
В списке pgsql-hackers по дате отправления: