Re: [HACKERS] Error "vacuum pg_proc"
| От | Bruce Momjian |
|---|---|
| Тема | Re: [HACKERS] Error "vacuum pg_proc" |
| Дата | |
| Msg-id | 199912270219.VAA27313@candle.pha.pa.us обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Error "vacuum pg_proc" (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [HACKERS] Error "vacuum pg_proc"
|
| Список | pgsql-hackers |
> I spent some more time looking into this, and found out that actually > the safe upper limit for btree index entries is not ~ BLCKSZ/2, but > ~ BLCKSZ/3. btree needs to be able to insert two items on every page, > but it *also* keeps an extra item (the "high key") on non-rightmost > pages. So if any item exceeds one-third the available space, you run > a risk of failure depending on what page it ends up on and what else > is on that same page. > > It turns out that for an index on a single text column, the maximum > safe text length is 2700 bytes. So the correct check for dangerous > procedure definitions in 6.5.* is This is another argument to try and get long tuples into 7.0. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: